Runtime Endpoints

This page lists public runtime endpoint families and their documentation roles.

API Host

https://api.pubfi.ai
Public endpoint families:
  • /healthz
  • /readyz
  • /
  • /.well-known/mcp.json
  • /version
  • /openapi.json
  • /reference
  • /v1/capabilities
  • /v1/capabilities/{capability_id}
  • /v1/gateway/...
  • /v1/api-keys
  • /v1/api-keys/{id}
  • /v1/account/credits
  • /v1/account/recharge-redemptions
  • /v1/account/usage
The API host also exposes a root MCP JSON-RPC endpoint and MCP discovery manifest for runtime clients that discover capabilities through the API OpenAPI surface. The hosted MCP client endpoint remains https://mcp.pubfi.ai.

MCP Host

https://mcp.pubfi.ai
Public endpoint families:
  • /
  • /healthz
  • /readyz
  • /version
  • /.well-known/mcp.json

Web Host

https://pubfi.ai
Public endpoint families:
  • /
  • /pricing
  • /blog
  • /blog/{slug}
  • /products/{slug}
  • /discovery
  • /discovery.md
  • /discovery/api/{source_slug}
  • /discovery/api/{source_slug}.md
  • /discovery/category/{slug}
  • /discovery/chain/{slug}
  • /discovery/compare/{slug-a}-vs-{slug-b}
  • /discovery/sources
  • /discovery/sources/page/{page}
  • /discovery/topic/{slug}
  • /discovery/topic/{slug}.md
  • /login
  • /privacy-policy
  • /terms-of-service
  • /agents.md
  • /llms.txt
  • /llms-full.txt
  • /sitemap.xml
  • /robots.txt
  • /discovery/agent-capabilities.json
  • /openapi/degov-openapi.json
  • /openapi/subscan-openapi.json
  • /.well-known/mcp.json
  • /.well-known/mcp/server-card.json
  • /.well-known/mcp-registry-auth (optional proof route; may return 404 when no proof is configured)
Legacy docs aliases on pubfi.ai redirect to the canonical docs site:
  • /docs -> https://docs.pubfi.ai
  • /docs/quickstart -> https://docs.pubfi.ai/getting-started/quickstart
  • /docs/degov-api -> https://docs.pubfi.ai/reference/provider-gateway-examples#degov-gateway-example
  • /docs/{path} -> https://docs.pubfi.ai/{path}

Docs Rule

Public docs can point to endpoint families and schemas. They should not publish private env vars, database URLs, credentials, raw account data, usage rows, or provider keys.