Getting started with Mansa API for AI agents.
Mansa API is designed for agents that need stable African market, location, and identity context without brittle web lookups. Use the machine-readable surfaces first, then move into the suite endpoints.
Start with /openapi.json and /llms.txt.
Issue a free key once, then send it as a Bearer token on every suite endpoint.
Call /health before heavier workflows if freshness matters.
Use the machine-readable surfaces first.
GET https://mansaapi.com/openapi.json
GET https://mansaapi.com/llms.txt
GET https://mansaapi.com/healthIssue the key once, then reuse it.
curl -X POST https://mansaapi.com/api/v1/keys \
-H "Content-Type: application/json" \
-d '{
"name": "Agent Operator",
"email": "agent@example.com",
"requested_suites": ["markets", "location"],
"primary_use_case": "AI agent or automation",
"target_countries": ["NG", "KE"],
"expected_volume": "testing"
}'Markets: prices, movers, forex, commodities, exchange metadata.
Location: countries, admin boundaries, holidays, Nigeria postcodes.
Identity: banks, mobile networks, currencies.
402: no API key was provided.
401: key is invalid or revoked.
429: daily limit reached; retry after reset or upgrade.
What agents should know about freshness and schema.
Markets endpoints currently target a 30-minute freshness window during market hours.
Location endpoints now include normalized admin fields such as country_code, admin_level_1_name, and admin_level_2_name where applicable.
Identity endpoints are reference-data surfaces, not real-time KYC or live HLR verification.