Simple, usage-based pricing.
£5 free credit on signup. No subscriptions, no commitments, no per-seat fees. Top up when you need to.
Geocoding
£0.50per 1,000 requests
- search · reverse · autocomplete
- structured search · places · parse
- locate (snap to road)
Routing
£2.00per 1,000 requests
- route · optimise · matrix · isochrone
- elevation · snap · compare
- find & route · search along route · batch geocode
Natural Language
£25.00per 1,000 requests
- natural-language query routing
- address correction & parsing
- intent detection across endpoints
Predict
Research Preview£1.00per request
- Spatial probability model
- H3-hex probability surface
- Behavioural profile inputs
All prices in GBP, exclude VAT where applicable. MCP tool calls are billed at the same rate as the underlying API endpoint.
How it works
No commitments, no minimums
Step 1
Sign up
Create an account at console.footstep.ai. £5 of free credit is applied to your account.
Step 2
Make API calls
Usage is metered per request and deducted in near real-time.
Step 3
Top up
Add credit when you need it, or enable auto-recharge.
Pricing FAQ
Common questions about billing
- What counts as a request?
- One request is one successful HTTP call to a Footstep endpoint, or one MCP tool invocation. Internal sub-calls don't count separately. find_and_route calls geocoding and routing under the hood, but you only pay for the routing tier (the outer call).
- Are MCP and REST billed separately?
- No. MCP and REST share infrastructure, and a tool call is billed at the same rate as the underlying endpoint. Same key, same balance, same invoice.
- What about failed requests?
- Failed requests (4xx and 5xx responses) are never billed. Only 2xx and 3xx count against your balance, so you never pay for our outages or your malformed inputs.
- Are retries billed?
- Each successful request is billed once. If your client retries a failed request and the retry succeeds, you pay for that one successful response. Standard idempotency rules apply.
- What happens when my balance hits zero?
- Requests return 402 Payment Required with a descriptive error. No surprise charges, no overage fees. Top up manually or enable auto-recharge in the console.
- Do you offer prepaid commitments?
- Above 1M requests a month, yes. Talk to us. We can structure annual commits with discounted per-call rates, dedicated rate limits, and SLA tiers tailored to the workload.
Volume pricing
Sustained usage above 1 million requests a month? Talk to us about volume pricing, dedicated infrastructure, on-prem deploys, and bespoke SLA tiers.
FAQ
Questions we hear most
If something here doesn't answer it, drop us a line at the contact form or open an issue on GitHub.
- What's the difference between the MCP server and the REST API?
- MCP is for AI agents. Your model picks tools at runtime over Streamable HTTP. REST is for everything else: backends, web apps, batch pipelines, plain HTTP. They share auth, response shapes, pricing, and data. Most teams use both, sometimes from the same product.
- Which AI agent runtimes are supported?
- Anything that speaks Streamable HTTP MCP. We've tested Claude Desktop, Claude Code, Cursor, Windsurf, Cline, Continue, OpenAI Agents SDK, Vercel AI SDK, LangChain (via the MCP adapter), and Google Gemini.
- How does pricing work?
- Pay-as-you-go per request, metered against the API key. Geocoding is £0.50 per 1,000. Routing (route, matrix, isochrone, snap, optimise, compare, find-and-route, search-along-route, batch geocode) is £2.00 per 1,000. Natural-language tools are £25.00 per 1,000. Predict is £1.00 per call. Failed requests aren't billed. Above 1M requests a month, talk to us.
- Do you offer enterprise or on-prem deploys?
- Yes, for teams with data-residency or air-gap requirements. Get in touch if your workload needs that.
- What about rate limits, status, and SLAs?
- Default rate limits are generous enough for typical agent workloads. SLAs scale with plan tier. Status updates and incident history live at status.footstep.ai (linked from the console). We aim for above 99.9% availability across both MCP and REST.
- Where does the data come from? How fresh is it?
- The road graph and POI index are refreshed weekly. Geocoding combines open address data, admin hierarchies, and place metadata. Elevation comes from open elevation datasets. Every response includes the underlying data version, so you can pin behaviour for reproducibility.