APIblaze for Claude and ChatGPT

Two things on this page: use APIblaze from your assistant, and make your own API directory-ready in one command.

Use APIblaze from your assistant

APIblaze’s own control plane is an MCP server. Add it to Claude (Settings → Connectors → Add custom connector, URL https://mcp.apiblaze.com) or to Claude Code:

claude mcp add --transport http apiblaze https://mcp.apiblaze.com

Sign in with your APIblaze account. Your assistant can then list and inspect your proxies, create a hosted MCP server for an API, mint and revoke API keys (shown once through a one-time link, never in the conversation), read usage, draft and apply access rules, explain a refusal, add a tenant admin and set rate limits. Destructive actions ask for confirmation.

Passing these checks means your MCP meets the requirements we can verify. Listing decisions are made by Anthropic and OpenAI.

Make your own API directory-ready in one command

npx apiblaze connector <project>

connector runs the directory checks against your proxy, applies the safe fixes (enables the MCP server, trusts Claude’s and ChatGPT’s OAuth clients, fills the docs URL and icon from your portal), asks for what only you know (privacy policy, support contact, example prompts, the five attestations), turns directory-ready mode on, and — when the report is green — writes the submission packet for both directories.

What directory-ready mode changes on your MCP server, and only there:

  • tool names capped at 64 characters and de-duplicated when the catalogue is regenerated;
  • PUT and DELETE marked destructive, PATCH and DELETE ask for confirmation, openWorldHint off unless you set it;
  • errors become “status: what the API said”; request ids, traces and timings are stripped from results; results above the client budget are cut with a visible marker;
  • a drained wallet answers “temporarily unavailable” (no checkout in a conversation);
  • OAuth sign-in is accepted on the published URL even for key-only proxies;
  • browser origins are limited to the directories’ own and the ones you allow;
  • 60 requests per minute per signed-in client;
  • the OpenAI domain-challenge file is served on your custom MCP domain.

Nothing changes while the mode is off.

What you need

  • A custom MCP domain: npx apiblaze domain add mcp.yourdomain.com --kind mcp --project <project>.
  • A public privacy policy, a support contact and documentation.
  • Three example prompts.
  • A reviewer test account: npx apiblaze connector reviewer <project> creates a username + password account on your tenant and stores it encrypted for the packet.

Check without changing anything

npx apiblaze check --directory-ready <project>

Prints the same report as the dashboard: “Claude: ready / ChatGPT: 2 blockers”, each blocker with the flag or field that fixes it.

Privacy

See the privacy policy: API key reveal window, sign-in data, directory test accounts, AI assistants. Support: apiblaze.com/support.