District truth for any listing pin.
Your listing app sends a coordinate. One call answers which district it stands in and how that district scores — the same engine behind the RE Intelligence app. Built for brokers, portals and the AI assistants your users already talk to. Resell it inside your own product; keep the "Powered by RE Intelligence" line.
Workflow — from a pin to a conclusion
Every answer is about the district the pin stands in, never the flat itself. Every answer carries a confidence word and the catalogue version, and every call writes one audit row you can reconcile against your invoice.
Endpoints
Base URL https://reintelligence.info/api · header x-api-key: rei_… (or Authorization: Bearer rei_…) · JSON in, JSON out · 60 calls a minute per key by default.
GET /v1/cities
The catalogue: every city with its district count and the catalogue version your answers were computed on.
GET /v1/cities/:city
A city's districts ranked by the app's own score, each with its band and id — ?limit= 1–200, ?band= one band — and the city's public page as the door.
GET /v1/superhero-dashboard
The retail service in one answer — what the Superhero Dashboard gives for a pinned shop, the live availability and estimate, the coverage rule and the quotation door; ?city= or ?country=.
POST /v1/resolve
{lat, lng, listingRef} → district id, name, city, country, score, band, confidence (inside · shared · nearest <km> · none), neighbours, a pin within 300 m of the edge names the neighbour, and a signed resolveId. "none" costs nothing.
GET /v1/districts/:id
The district's app-computed score and band — Prime · Strong · Moderate · Caution · Avoid.
GET /v1/districts/:id/momentum
Score and band plus the indicator lines the app shows, the six lens counts (cafés · restaurants · retail · schools · transit · hotels) and the night-light momentum (year-on-year %, month-on-month %, badge, confidence).
POST /v1/report
The official Property Scout report for the district your pin resolved to — {resolveId, lang, compare}. Issued into the registry and answered as a permanent link (reintelligence.info/r/<number>); compare 0–8 adds nearby + similar context districts. One report per resolveId.
GET /v1/me
Your balance, spent tokens, limits and today's usage — the same numbers as your invoice.
Quick start
curl -X POST https://reintelligence.info/api/v1/resolve \
-H "x-api-key: rei_YOURKEY" -H "content-type: application/json" \
-d '{"lat": 24.7136, "lng": 46.6753, "listingRef": "L-10492"}'
{ "confidence": "inside", "districtId": 1234, "name": "Al Olaya", "city": "Riyadh", "country": "SA",
"score": 84, "band": "Prime", "km": 0.41, "nearBorder": false, "neighbours": [ … ],
"resolveId": "eyJwaW4i…", "catalogueVersion": "13734-14167", "tokens": { "charged": 1, "balance": 99999 },
"note": "The district the pin stands in — the answer is never about the flat itself." }
What you never get: the indicator values and weights behind a score. The method is the product; you receive conclusions — scores, bands, momentum, the lines the app itself shows — with the reference period and source beside every figure.
For AI assistants — the MCP server
The same seven tools over the Model Context Protocol, so Claude, ChatGPT and your own agents can ask "which district is this pin in, and how does it score?" in a conversation. Four of them answer with no key at all — add the URL and ask; the three paid ones take your key, your tokens, the same audit rows.
Connect
Server URL https://reintelligence.info/api/mcp · transport Streamable HTTP · no sign-in for the four free tools · Authorization: Bearer rei_… for the paid three. Add it as a custom connector / remote MCP server in your assistant — or turn it on from the directory below.
Tools
Free, no key: list_cities · city_districts · district_summary · superhero_dashboard. With a key: resolve_pin (1) · district_momentum (5) · district_report (5,000–20,000 by size). Each returns structured JSON and a readable text copy, with the catalogue version.
Behaviour
Read-only tools, no side effects. The assistant is told the answer is about the district, never the flat, and that the paid calls cost tokens — so it asks before fanning out.
Use it in your AI chat
One tap, no key: RE Intelligence in Claude's connector directory. More assistants are added here as their directories list it.
// JSON-RPC over POST — what an assistant sends
{ "jsonrpc": "2.0", "id": 1, "method": "tools/call",
"params": { "name": "resolve_pin", "arguments": { "lat": 25.2048, "lng": 55.2708 } } }
Tokens and prices
Weighted, never flat — a lookup costs little, a report costs what it is worth. Opening price USD 25 per 100,000 tokens; wholesale tiers for resellers by agreement. Tokens are bought in advance; a call that cannot be paid answers 402 and charges nothing.
| Call | Tokens | At USD 25 / 100K | Status |
|---|---|---|---|
| Resolve a pin to its district | 1 | USD 0.00025 | live |
| District score + band | 1 | USD 0.00025 | live |
| Momentum + indicator block | 5 | USD 0.00125 | live |
| District report (the Scout report for the resolved district, permanent /r link) | 5,000–20,000 by size | USD 1.25–5.00 | live |
| Analyst question about a district | 100 | USD 0.025 | next release |
| Catalogue list · your usage (/v1/me) · a pin that resolves to none | 0 | — | live |
Buy tokens
With your key: POST /api/v1/checkout {"tokens": 100000} answers a hosted payment page (Mada · Apple Pay · Visa/Mastercard · STC Pay, billed in SAR — USD 25 ≈ SAR 94 per 100K). Pay there; the tokens are credited to your key as soon as the payment is confirmed, and GET /api/v1/me shows the new balance. Prefer an invoice and bank transfer? Email info@reintelligence.info — tokens are credited on receipt.
Resell it
Show the conclusions inside your own product and price them as you like; a district report resold at USD 8–10 is the pattern we designed for. Keep "Powered by RE Intelligence" on anything displayed.
One key per partner
Per-key rate limits, a balance you top up, and an audit row per call — your invoice is the sum of those rows, nothing hidden.
Accuracy you can check
Accuracy means "the right district for the pin". Every audit row keeps the pin, the district and the confidence word, so a disputed answer is a thirty-second check.
Request access
Keys are issued by hand for now. Tell us who you are and what you are building; we answer by email within two working days with your key and the first tokens.