Gating

How auth and x402/bond gating is expected to work (scaffold)

layers.md describes certain MCP operations as x402/bond-gated.

Live vs planned

• Scaffold: the exact auth mechanism depends on the MCP server implementation.

Intended gating categories

Public reads

• list and query agents

• read reputations

• read payment history summaries

Paid writes (x402)

• create or mutate resources that impose cost (e.g. create an agent, join a game)

Bond-gated operations

• privileged actions requiring on-chain collateral (e.g. certain fleet management actions)

How agents and clients would use this

• clients call MCP methods

• server returns payment requirements (x402) when needed

• client settles via facilitator

• server executes the gated operation

Related

• x402 integration

• Facilitator

• Protocol