Self-serve identity setup
Create identities, manage credential proof, publish pages, configure forms, and control visibility from the app.
Docs
Build the identity first. Integrate only when the workflow is clear.
Most teams should start in the product, then use the public discovery, OAuth, protected resource, and MCP references when the identity needs to connect with software.
Live signupQuick startAPI catalogMCP tools
Agent conversion playbook
How software agents discover, evaluate, and subscribe.
Do not scrape HTML first. Use machine documents and public MCP tools, then OAuth for paid checkout.
GET /.well-known/agent-discovery.json — pricing tiers, limits matrix, conversion path, sample prompts.
POST /mcp tools/call list_plans (and get_limits_matrix / get_conversion_path) for structured plan data.
OAuth via auth.pox.me (openid offline_access profile email); then identity MCP whoami + get_billing_access.
Authenticated POST api.pox.me/billing/checkout to open Stripe checkout for Starter/Professional/Team.
Humans: /sign-up → free plan or paid → /app → create first identity → attach a credential.
curl -sS https://pox.me/.well-known/agent-discovery.json | jq .
curl -sS -X POST https://pox.me/mcp \
-H 'content-type: application/json' \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"get_conversion_path"}}'Entry points
Three ways to use pox.me.
Choose the path that matches the job: human operators use the app, products use the references, and agents use the discoverable tool surfaces.
Product integration
Use public metadata, API catalog entries, and authenticated resources when your product needs identity data.
Agent client access
Use machine-readable discovery, OAuth metadata, and MCP surfaces when software needs to understand and act.
Quick start
The practical order for teams and agents.
Start with a real identity because it gives every integration decision concrete context.
Recommended setup path
Reserve the handle, publish the claim, add verified proof, choose access, then wire integrations after the page and workspace are doing real work.
Create an account and reserve the handle for the person, team, product, or agent identity.
Add profile context, links, verified credentials, and a clear call to action.
Choose access if the workflow needs private workspace, protected APIs, billing-backed entitlements, or agent usage.
Use public discovery references before wiring OAuth, MCP, or API calls into your product.
References
Machine-readable docs for discovery, authentication, and execution.
These are the references product teams and agent clients should use before hard-coding assumptions about identity, access, or tools.
Integration references
Agent discovery manifest
https://pox.me/.well-known/agent-discovery.json
Agent conversion hub
https://pox.me/agents
API catalog
https://pox.me/.well-known/api-catalog
Protected resource metadata
https://pox.me/.well-known/oauth-protected-resource
OpenID configuration
https://auth.pox.me/oidc/.well-known/openid-configuration
Public discovery MCP
https://pox.me/mcp
Identity MCP
https://mcp.pox.me/mcp
Commerce MCP
https://api.pox.me/agentic/mcp
LLMs overview
https://pox.me/llms.txt
Example calls
curl https://pox.me/.well-known/api-catalog
curl https://pox.me/.well-known/oauth-protected-resource
npx mcp-remote https://mcp.pox.me/mcp
curl https://api.pox.me/billing/access \
-H "Authorization: Bearer <access-token>"Docs are not the first step
Create a concrete identity, then connect the systems around it.
A real handle, public page, verified credential, and access state will make API and agent integration decisions much clearer.