MCP and AI assistants
The same calculation engine, exposed to AI assistants through the Model Context Protocol.
Two doors, one engine
The REST API and the MCP server call the same deterministic engine, so an assistant and your backend always agree on an answer.
Anonymous use is capped
Unauthenticated MCP traffic is free, deliberately small and rate limited per client address. It is there for trying things out, not for production workloads. Sustained or automated use should be authenticated.
Authenticated use shares your quota
When MCP calls are authenticated with an API key, they count against the same account-wide monthly quota as REST calls. There is no separate, cheaper pool, and no way to bypass metering by switching transport. Limits are on the Rate limits and quotas page.
Connecting an assistant
Setup instructions for ChatGPT, Claude and Claude Code are on the Connect page.
Choosing between them
- Use MCP when a human or an assistant is asking a question conversationally.
- Use the REST API when software needs a guaranteed contract, headers and error codes.