Install and API
Connect the MCP server to ChatGPT or another MCP client, or call the open /v1 API. Read tools and the API need no key and no account.
The ChatGPT app
The ChatGPT app runs on the MCP server described below. Once OpenAI lists it in ChatGPT, the web version of this page links to it; until then, this page has no Open in ChatGPT link.
Other MCP clients
The MCP server answers at https://mcp.act60.business/mcp over streamable HTTP. Read tools need no key and no account, and requests are rate-limited per IP address. A client that takes a JSON list of servers connects with:
{
"mcpServers": {
"act60": {
"type": "streamable-http",
"url": "https://mcp.act60.business/mcp"
}
}
}
Each tool page lists the tool's MCP tools and its demo prompt. Three prompts to try once connected:
- What Act 60 compliance dates are coming up for me?
- What does Act 60 say about the annual report?
- Compare keeping my decree with requesting the Act 38-2026 terms
Custom GPT
While a custom GPT for this site is available in ChatGPT, it calls the API described below, and the web version of this page links to it.
API
The API has its own address, separate from this site. The full address of its OpenAPI 3.1 document, which ends in /v1/openapi.json, is listed under Optional in llms.txt. The API needs no key and no account, and requests to /v1/estimate and /v1/canon/ask are rate-limited per IPv4 address or per IPv6 /64 network.
POST /v1/estimateruns the Regime Calculator and returns every line with its rule reference.POST /v1/canon/askmatches a question to a verified question page and returns that page's two-sentence answer, citations, regime tag, verified-on date and address, in English or Spanish. When no page is close enough, or no version of the closest page was verified in the last 90 days, it returns the codeno_citationand no answer.GET /v1/healthreports whether the API is up and how many published question pages its index holds, with each language version counted separately.
Every JSON response from these endpoints carries _meta with the signature line and a one-line trace: sources, a date and steps. When /v1/canon/ask returns an answer, the date in both lines is that page's verified-on date; in an estimate, it is the date a person verified the calculator's rules, or pending until then; in any other response, including a refusal, it is the date the response was made.
API keys
A free API key raises the rate limit for another builder's agent and records which key made each call. Read tools, the API and the MCP server work the same without one. Send the key as Authorization: Bearer <key> to the API or to the MCP server; requests that carry it are counted per key instead of per address, at the limits listed with the request form on the web version of this page. The form asks for a name or organization, what the key is for and a contact email. The key is shown once, on that page, and only a hash of it is stored.
Request an API key
A free key raises the rate limit to 180 requests a minute on the API and 360 on the MCP server, counted per key instead of per address. Read tools answer the same with or without one.
Key requests are not open yet. Read tools, the open API and the MCP server work without a key.