Keys, scopes & limits
Public keys for browsers and apps, locked to your origins and the APIs you tick; secret keys for servers; short-lived tokens minted from a secret key. Every response carries X-RateLimit headers.

Developer tools
Public and secret keys with origins and scopes, an API reference generated from the spec the API is checked against, an MCP server for AI agents, and a console for apps, usage and billing.

A public key is limited to your origins and the APIs you tick, a secret key stays on your server, and a rotated key keeps working for 24 hours.
Every error has the same JSON shape with a code, a message and a link to its explanation; every response carries your remaining limits.
The MCP server gives an AI assistant seven read-only tools on your key: places, addresses, directions, transit, map images and incidents.
Public keys for browsers and apps, locked to your origins and the APIs you tick; secret keys for servers; short-lived tokens minted from a secret key. Every response carries X-RateLimit headers.

Create apps and keys, watch usage by endpoint and day, wire up webhooks, invite your team and see invoices. In development: opening in stages.

Every public endpoint with its parameters, responses and errors, generated from the same OpenAPI spec the API is checked against.
Point an AI assistant at the MCP endpoint with your key and it gets seven read-only tools: search, nearby places, reverse geocoding, directions, transit plans, map images and incidents. Metered like any call.
POST /mcpTyped requests and responses for every endpoint, plus helpers for style URLs and map images. In development: not published yet.
Sign in with your identity provider over OIDC or SAML, and provision members with SCIM. In development, with the console.
{ "mcpServers": { "tareky": { "url": "https://api.tareky.com/mcp", "headers": { "Authorization": "Bearer tareky_sk_…" } } }}During early access we issue keys by hand: leave your email and tell us what you are building. Self-serve keys come with the console.
A typed TypeScript SDK generated from the OpenAPI spec is in development. Until it is published, the API is plain HTTPS and JSON.
SSO over OIDC and SAML, and SCIM provisioning, are built for organisations and open with the console.
Tell us what you are building. During early access we issue keys by hand, and we email you once when yours are ready.
هذه الصفحة متوفرة بالعربية أيضًا.
اقرأها بالعربيةئەم پەڕەیە بە کوردیش هەیە.
بە کوردی بیخوێنەوە