# Dapper Developer Portal

> Documentation portal for the Dapper Public API: political and regulatory
> intelligence for Latin America, as read-only data (12 countries,
> 8 data domains: regulations, bills, actors, consultations, schedules, news, transcripts, documents).

## Portal pages

- [Overview & quickstart](https://developers.dapperglobal.com/en): what the API is, first request in 5 steps
- [Use cases](https://developers.dapperglobal.com/en/use-cases): regulatory monitoring, legislative tracking, political risk, voting analytics, cross-country benchmarking, AI copilots — with FAQ
- [Data coverage](https://developers.dapperglobal.com/en/data): domains, per-country coverage matrix, featured sources
- [API reference](https://developers.dapperglobal.com/en/reference): interactive OpenAPI reference
- [MCP integration](https://developers.dapperglobal.com/en/mcp): connect Claude, ChatGPT, Cursor, and other MCP clients
- [Connect Claude](https://developers.dapperglobal.com/en/mcp/claude): step-by-step setup for Claude web, desktop and Claude Code
- [Connect ChatGPT](https://developers.dapperglobal.com/en/mcp/chatgpt): step-by-step setup for a custom MCP plugin in ChatGPT
- [Connect Gemini CLI](https://developers.dapperglobal.com/en/mcp/gemini): step-by-step setup for ~/.gemini/settings.json
- [Connect the Gemini app](https://developers.dapperglobal.com/en/mcp/gemini-app): adding Dapper as a custom app in Gemini (AI Pro or Ultra, US personal accounts)
- [Connect Gemini Enterprise](https://developers.dapperglobal.com/en/mcp/gemini-enterprise): admin setup of a custom MCP server connector, including the OAuth client registration
- [Connect Microsoft Copilot Studio](https://developers.dapperglobal.com/en/mcp/copilot-studio): step-by-step setup for a Copilot Studio agent
- [Data freshness](https://developers.dapperglobal.com/en/status): live last-update times per country and domain

Spanish versions live under https://developers.dapperglobal.com/es.

## API

- Base URL: https://api.dapperglobal.com
- Full agent guide: https://api.dapperglobal.com/llms.txt
- OpenAPI spec: https://api.dapperglobal.com/openapi.json
- MCP endpoint (streamable HTTP): https://api.dapperglobal.com/mcp
- MCP auth: interactive clients use the OAuth browser login discovered at https://api.dapperglobal.com/.well-known/oauth-authorization-server/mcp. Without a browser, an API key works three ways: the X-API-Key header, Authorization: Bearer <api key>, or the client_credentials grant at POST https://api.dapperglobal.com/oauth/token (client_id = the API key's id, client_secret = the API key). Keys restricted by country or domain are not accepted on /mcp.
- Public, no key required: GET /v1/health (freshness), GET /v1/countries (coverage)
- Data endpoints require the X-API-Key header.
- Routes are domain-first: /v1/{domain}?country_code=BR,CO (comma-separated, optional — defaults to the key's country scope); detail lookups are /v1/{domain}/{id} with no country.