Open protocol · Hosted API · Apache 2.0
The geo foundation
for AI.
Resolve any place to a stable geopath, anchor local activity to it, and serve it to LLMs and agents — over one API. The protocol underneath is open. The hosted API on top is the product: one key, pay as you go.
$ curl https://api.geofeed.ai/resolve \
-H "Authorization: Bearer gf_live_..." \
-d '{"q": "padaria na praça do tatuapé"}'
{
"geopath": "bra/sp/sao-paulo/tatuape",
"confidence": 0.94,
"type": "bra-neighborhood",
"credits_used": 1
}One API key works across every endpoint. New keys start with 10,000 free credits.
One key, every endpoint
Resolver
POST /resolve
Free-text place or address → a stable SubdivisionPath, confidence score, and embedding. Powered by the open subdivision-resolver model.
Feeds
GET /feeds/{geopath}
Publish and query structured local activity (Actor-Verb-Object) anchored to a geopath. JSON for apps, Markdown for RAG.
Render
md.geofeed.ai/{geopath}
Any geopath as clean, LLM-ready Markdown context — the way r.jina.ai renders a URL, but for a place.
MCP
mcp.geofeed.ai
A hosted Model Context Protocol endpoint. Give any MCP-compatible agent native access to the geo registry.
Geographic hierarchy as semantic path
Open at the core, hosted for convenience
The protocol is free
Spec is Apache 2.0, permanently. Registry reads are free — it's the DNS of the protocol, never behind a paywall.
The model is open
The subdivision-resolver weights are public on HuggingFace. Run it yourself, or let the hosted Resolver do it.
You pay for managed
Credits meter the hosted convenience — resolution at scale, serving, render, MCP. Exactly the Jina model.
Start with 10,000 free credits.
One key for every endpoint. No subscription — top up when you need more, billed through Stripe.