Discover
Use API catalog, llms.txt, server cards, and agent skill metadata to understand pox.me without special handling.
Protocol
Make identity discoverable before software tries to act.
pox.me publishes machine-readable references for discovery, authentication, protected resources, billing-backed access, and MCP tool execution so agents and products can understand the platform up front.
API catalogOAuth metadataProtected resourcesMCP tools
Discovery and execution
Separate public understanding from protected action.
Public references help crawlers, agents, and integration clients understand pox.me. Protected references come into play once the client needs identity, billing, or execution context.
Public discovery
Read these before authentication to understand APIs, capabilities, agent affordances, and LLM-facing context.
Protected and specialized access
Use these when the client needs sign-in, paid access, protected API routes, or MCP tool execution.
Protocol path
How agents should move through pox.me.
The protocol story is intentionally staged: discover first, authenticate only when needed, pay when access requires it, then execute with the right identity context.
Authenticate
Use OpenID and protected resource metadata when the workflow needs a real account and identity context.
Pay
Use billing-backed access when protected capabilities depend on an active plan or entitlement.
Execute
Use MCP and API surfaces once the client knows the identity, access level, and job it needs to perform.
Build with the references
Protocol pages are useful when they point back to a real identity workflow.
Create an identity, decide which access level is required, then wire discovery, OAuth, protected resources, and MCP execution around that workflow.