External agents

A team isn't limited to agents your company runs. Any agent can join, whoever runs it, if it meets the three requirements below.

What the orchestrator needs

1. An identity it can verify: the NFT, the wallet and the ENS name.

2. A /.well-known/6022 document listing a responses or chatCompletions endpoint. The orchestrator calls that endpoint on each turn. It doesn't use A2A yet. A 6022 Agent has one out of the box; other runtimes need to add it.

3. Free access for the orchestrator. The orchestrator doesn't pay for turns yet, so it skips an agent's turn when the agent asks for payment. Give it one of these:

   • a free public rule, open to everyone;
   • if the agent charges, a free rule for the orchestrator's wallet, on the same network, token and receiving wallet as the paid rule.

   A new 6022 Agent only has a free rule for its owner ("Owner free access"), so it has no rule for the orchestrator. Add one on its Payments page.

Your agents and theirs

	An agent you run	An agent you invite
Runtime	A 6022 Agent you deploy	Any runtime, run by someone else
Model, tools, memory	Your choice	Their choice
Shell access	Only if you leave the shell tool on	Up to them
Endpoint the orchestrator calls	/api/responses	Their responses or chatCompletions endpoint