One API source of truth
The quickstart, endpoint registry, OpenAPI document, remote MCP tool registry, and shared Yucatán service are checked for drift. Repository-ready does not mean deployed: customer access remains disabled until migrations, secrets, source rights, and remote-client acceptance pass in a non-production environment.
API v1 + scoped keys
Six operations share one contract, provenance model, quota, and revocation boundary.
Remote MCP
Streamable HTTP + OAuth 2.1 (Clerk CIMD) for Claude/ChatGPT, or a pymx_live_ key. Still needs post-deploy remote-client acceptance.
First request
Store the one-time key as PYRAMETRICS_API_KEY. Never place it in browser code or a URL.
curl --fail-with-body --silent --show-error \
-H "Authorization: Bearer $PYRAMETRICS_API_KEY" \
-H "Idempotency-Key: catalog-first-request" \
"https://pyrametrics.com/api/v1/catalog"Prepared MCP configuration
It remains disabled until the remote origin passes acceptance.
[mcp_servers.pyrametrics]
url = "<PYRAMETRICS_ORIGIN>/mcp"
bearer_token_env_var = "PYRAMETRICS_API_KEY"
enabled = false
# Enable only after the deployment owner confirms the remote acceptance gate.Endpoint groups
AI / Pyra
/api/pyra/chat · /api/gemini/docs
Market Data
/api/market · /api/semantic/context · /api/data-products/yucatan/assessment · /api/data-products/yucatan/explorer
Developer Data API & MCP
/api/developer/keys · /api/v1/catalog · /api/v1/geographies · /api/v1/yucatan/profile
Identity & Account
/api/auth/eve-token · /api/user/init · /api/me/entitlements · /api/me/is-admin
Billing & Stripe
/api/billing/checkout · /api/billing/portal · /api/stripe/webhook
/api/email
Operations & Health
/api/health