One call, one execution record
Every call carries your invocation_id. Services records the execution before calling the provider and never runs the same id twice, so a retry is never charged twice.
ZGI Services
One credential and one set of call rules for public holidays, exchange rates, scholarly works, weather, earthquakes and more, over an HTTP API or MCP.
At a glance
Section titled “At a glance”| API base URL | https://services.zgi.im/v1 |
| MCP endpoint | https://services.zgi.im/v1/mcp |
| Authentication | Authorization: Bearer <service credential> |
| Format | JSON, request bodies up to 64 KiB |
| Status | /health/ready |
Reconcilable results
Each response states the outcome and usage units. The call log is scoped to your caller and can be filtered and summarized by time, capability, provider and outcome.
HTTP and MCP are equivalent
Every capability is an HTTP endpoint and an MCP tool of the same name, with identical arguments, validation and execution records.
Facts, not prices
Services reports outcomes and usage (requests, records); it never prices, charges or refunds. Billing rules belong to the caller.
Start here
Section titled “Start here”QuickstartYour first call in five minutes.
ConventionsRequests, invocation ids, outcomes and retries.
MCPUse the capabilities from Claude, Cursor and other agents.
Capability referenceFields, providers, limits and real examples.