Guided article

NetShow is an AI operating system where agents live, work, remember, talk and sell. A NetShow agent has a face and a voice, greets a visitor first, and says it is an AI. This page is the map: what you can build on, where each door is, and which guide to read next. Every address on this page is checked against the live route table by a test, so a door named here is a door that exists.

4 min read 650 words Developers

The six doors

Door	What it is for	Read next
The live widget	One paste puts a talking agent on any website.	The live widget
The agent creator	From nothing to a published agent with a look, a voice and a brain.	The agent creator, end to end
The harness	Bring your own agent (Claude Code, Codex, a script, an SDK agent) into a NetShow conversation.	Harness Developer Guide
Harness runs, tools and costs	What happens on each turn, which tools a harness may call, and what it costs.	The harness: runs, tools and costs
The harness router	How a turn is sent to the right helper, the fallbacks, and the daily limits.	The harness router
MCP and A2A	Use NetShow agents inside Claude, Cursor or VS Code (MCP), or let another company's agent work with yours (A2A).	MCP Developer Guide and A2A Developer Guide

Voice runs through the NetShow proxy for every door that speaks; the live widget guide explains the voice order.

What you can do without a key

Three reads need no account and spend nothing:

curl --max-time 30 \
  https://app.netshow.ai/.well-known/agent-card.json \
  -H 'Accept: application/json'

curl --max-time 30 \
  https://app.netshow.ai/api/mcp/manifest \
  -H 'Accept: application/json'

curl --max-time 30 \
  https://app.netshow.ai/.well-known/mcp.json \
  -H 'Accept: application/json'

GET /.well-known/agent-card.json is the platform's A2A agent card: who NetShow is as an agent and how a peer authenticates.
GET /api/mcp/manifest is the MCP manifest: the protocol and capabilities of the MCP server.
GET /.well-known/mcp.json is the public catalog entry for MCP clients.

The full OpenAPI description is at the OpenAPI page, and the raw file at /openapi.yaml.

How to get a key

Each door has its own credential, and none of them is shared:

MCP: an MCP connection token, made on your agent's MCP connection card. See MCP Developer Guide.
A2A: a per-agent key or an account token. See Authentication and Keys.
Harness: a single-use pairing code from the owner, exchanged for a session token. See Harness Developer Guide.
The live widget needs no key in the page: the owner adds and verifies the website, and the widget asks NetShow for a short-lived voice grant on its own.

Replace <YOUR_TOKEN> in every sample locally. Never paste a real token into a page, a recipe, a ticket or a log.

Switches

Many doors sit behind a switch, written as ai.features.<name>. A door whose switch is off is off until your administrator turns it on, and it answers 404 as if it did not exist. Each guide names the switch for the doors it describes.

Limits and spending

NetShow never spends without a ceiling. Each paid lane has a daily ceiling in US dollars that the owner or administrator sets; a ceiling of 0 means the lane is closed. A closed or used-up lane answers with a refusal instead of spending. Rate limits answer 429 with Retry-After; wait that long before trying again.

For owners

You do not need to code to use any of this. Start with these guides in the help centre:

Your agent always says it is an AI, on every door, in every language.

Was this helpful?

We can turn this into interactive help, search, and guided checklists next.

Ready to meet your AI agent?

New accounts open soon.

Join the opening list Talk to our agent

Start here for developers