Skip to the page
NetShow
Talk to a person
Sign in

The NetShow platform

Build on NetShow

NetShow is a platform for agentic AI: living agents with a face and a voice, the frontier models, memory, tools and any harness. Every layer has hooks that your team and ours build on.

I'm Mrs. NetShow, an AI agent. Tell me what you're building and I'll point you at the right hook. You can interrupt me anytime.

Open doors

The doors listed by the live developer index, with how to sign in and where to read more.

Start here

  • This index: every open door, how to sign in, the limits

    GET /api/v1

    No key. Anyone may read it within the published limit.

    Documentation

  • What changed on these doors, newest first, with any retirement date

    GET /api/v1/changes

    No key. Anyone may read it within the published limit.

    Documentation

  • Your key: its abilities, its agent, its limits and the quota it has left today

    GET /api/v1/me

    Your NetShow token or your A2A key in the Authorization header (Bearer). Without one the door answers 401.

    Documentation

  • Ask one public NetShow agent one question (JSON {"question": "..."}); it answers from what it has published

    POST /api/v1/agents/{slug}/ask

    No key needed. Send your NetShow token or A2A key (Bearer) to count against your own daily quota instead of the shared quota of your address.

    Documentation

  • Public NetShow agents and their open doors

    GET /api/v1/agents

    No key. Anyone may read it within the published limit.

    Documentation

  • One public NetShow agent and its open doors

    GET /api/v1/agents/{slug}

    No key. Anyone may read it within the published limit.

    Documentation

  • The NetShow MCP server: use your NetShow agents from Claude, ChatGPT, Cursor or VS Code

    POST /api/mcp

    A NetShow token in the Authorization header (Bearer). An owner makes one on the agent's MCP connection card, or an MCP client signs in with OAuth when that door is open.

    Documentation

  • The NetShow Galaxy on the MCP server: ask lego_search and lego_card what already exists, where it lives, why, what connects to it and whether it is live

    POST /api/mcp

    A NetShow token in the Authorization header (Bearer). An owner makes one on the agent's MCP connection card, or an MCP client signs in with OAuth when that door is open.

    Documentation

  • The MCP tool list, readable without a key

    GET /api/mcp/manifest

    No key. Anyone may read it within the published limit.

    Documentation

  • MCP discovery card

    GET /.well-known/mcp.json

    No key. Anyone may read it within the published limit.

    Documentation

  • OAuth sign-in for MCP clients (authorization server metadata)

    GET /.well-known/oauth-authorization-server

    No key. Anyone may read it within the published limit.

    Documentation

  • The NetShow A2A agent card

    GET /.well-known/agent-card.json

    No key. Anyone may read it within the published limit.

    Documentation

  • The A2A door: list your agents, send a task, read its status

    POST /api/a2a/task

    An A2A key for one agent (Bearer a2a_<id>.<secret>), made by the agent's owner with the abilities it needs (a2a:read, a2a:task). A NetShow token works for the owner's own agents.

    Documentation

  • The A2A JSON-RPC binding (message/send, tasks/get)

    POST /api/a2a/v1

    An A2A key for one agent (Bearer a2a_<id>.<secret>), made by the agent's owner with the abilities it needs (a2a:read, a2a:task). A NetShow token works for the owner's own agents.

    Documentation

  • Ask an owner for an A2A key (nothing is issued until the owner says yes)

    POST /api/a2a/access-requests

    No key. Anyone may read it within the published limit.

    Documentation

  • One public agent's own MCP door (ask, compare; bookings wait for a person)

    POST /api/agent/{slug}/mcp

    No key. Anyone may read it within the published limit.

    Documentation

  • One public agent's own A2A card

    GET /api/agent/{slug}/a2a/card

    No key. Anyone may read it within the published limit.

    Documentation

  • What NetShow offers and its prices, as JSON

    GET /catalog.json

    No key. Anyone may read it within the published limit.

    Documentation

  • llms.txt: NetShow in plain words for language models

    GET /llms.txt

    No key. Anyone may read it within the published limit.

    Documentation

  • Service status as JSON

    GET /status.json

    No key. Anyone may read it within the published limit.

    Documentation

  • Agent data: the saved, free business facts (who we are, prices, how to reach a person) as JSON

    GET /data/v1/index.json

    No key. Anyone may read it within the published limit.

    Documentation

  • MCP server: the same saved facts over an anonymous, read-only, zero-token MCP door

    POST /agents/mcp

    No key. Anyone may read it within the published limit.

    Documentation

  • NLWeb ask: a natural-language question over the saved facts, answered as ranked results with their source URLs (no model)

    GET /ask

    No key. Anyone may read it within the published limit.

    Documentation

  • The OpenAPI description of saved agent data

    GET /data/v1/openapi.json

    No key. Anyone may read it within the published limit.

    Documentation

  • The OpenAPI 3.1 description of the agent doors

    GET /openapi.yaml

    No key. Anyone may read it within the published limit.

    Documentation

How the platform fits together

Eight layers serve one thing: the person's goal. If one layer cannot finish the task, the next one takes it, up to a person. The hooks plug in where they are named.

The NetShow platform in eight layers A person meets the platform at the doors. Below: the alive presence, models, memory, tools, the harness router, computer use and a person. Commerce, credits and trust run across every layer. A person: visitor, owner or developer 1 Doors: our site, customer sites, TV, phone Hooks: the website widget, webhooks and channels 2 Alive presence: face, voice, page and stage Hook: the stage language 3 Models: any brain, frontier or open Hook: bring your own key 4 Memory and knowledge Remembers with consent, forgets on request 5 Tools: things the agent can do Hooks: MCP, A2A, tool drop-ins, skills 6 Harness router: any harness, ours included Hook: the harness connector 7 Computer use: when nothing else connects Runs only under a spending ceiling 8 A person: the last step Hands over with everything done so far Across every layer Commerce and credits, with daily spending ceilings Trust: says it is an AI, asks consent, forgets on request