Connect agents to the Aurato Graph.
The Aurato MCP server provides tools that AI agents can use to interact with the Aurato Graph.
Getting started
Connect your agent in three steps:
- 1
Create your Aurato account
Loading your account…
- 2
Connect to the Aurato MCP
Connect to
https://mcp.aurato.io,
then sign in to Aurato and approve access. - 3
Ask your first question
Ask your agent a payments question, for example:
Which payment methods are available in India?
Connection
Choose your AI tool below. Connect with OAuth, then sign in to Aurato, and approve access - no key needed.
Add a custom MCP connection using https://mcp.aurato.io.
Choose OAuth, then sign in to Aurato, and approve access.
Or run these commands in your Codex terminal:
codex mcp add aurato --url https://mcp.aurato.io
codex mcp login auratoConnect with an API key
Use an API key for custom scripts, custom agents or clients without OAuth support.
Create a key in Account → Tokens → Keys,
and copy it when it appears (only shown once).
Configure your client to send this header to https://mcp.aurato.io as an alternative to OAuth:
Authorization: Bearer AURATO_API_KEYReplace AURATO_API_KEY with your key.
Keep it out of shared repositories and screenshots.
Tools
Aurato provides ten tools: six for exploring Graph data and four for identifier lookups.
| Tool | Description |
|---|---|
list_available_data | Discover the Aurato datasets and which tools to use for each: Atlas entities, cards, IIN, MCC, BSC and BIC. |
search_aurato | Search or browse one Graph collection with API-equivalent filters and cursor pagination. Omit query to browse. Keep filters and sort unchanged when continuing with meta.page.after. Returns published records, IDs and canonical links. Cards use schema 2: fields and field_context are canonical; attributes contains deprecated aliases. |
get_entity | Retrieve one canonical entity or card with the API's attributes and metadata. Preserve source references and rights restrictions where provided. Optional entity expansions: relationships, measurements, sources. For markets, include scheme_profile to retrieve the latest annual Schemes profile in data.scheme_profile, with source references, scoped breakdowns, qualifications and panel years. Preserve units and separate source scopes; do not add overlapping breakdowns. An unpublished profile is null. Cards support relationships only; schema 2 fields and field_context carry current values, currencies and conditions. Missing values are not zero or no. Use the four lookup tools for identifiers. |
get_measurements | Read current measurements, monthly payment-method history from August 2016, or annual market Schemes transaction history for 2015–2025. Set period_basis=calendar_month for method-by-market users, transactions and TPV; context_id selects one market. Set calendar_year with collection=markets for a years/types matrix, optionally filtered by scheme_group and inclusive YYYY bounds; annual page_size and offset count years. Continue with meta.page.next_offset. Preserve units, periods, confidence and source references where provided. Missing observations remain null or unavailable; do not interpolate, treat missing as zero or add overlapping users as unique people. |
get_relationships | Read direct relationships or retrieve related entities in target_collection. For a market's payment methods, set collection=markets and target_collection=payment-methods. Include measurements and sources for the market context. Relationships include context_entity_id for market-specific support; null means unspecified scope, not worldwide coverage. Derived market coverage is identified by derived_from_relationship_ids. |
get_sources | Retrieve the source references available for an entity and its API-projected measurements and relationships. Cite the returned source URLs; a reference is not the full source document. A market's annual Schemes profile also includes its scoped source references when requested through get_entity. |
lookup_iin | Look up a card IIN/BIN prefix through published Graph data and rights checks. Send only the first 6–11 digits, never a full card number. |
lookup_mcc | Look up a Merchant Category Code through published Graph data and rights checks. Preserve leading zeros and the returned code-set qualifications. |
lookup_bsc | Look up a Bank Sort Code or national clearing code through published Graph data and rights checks. Supply system when needed to disambiguate. Preserve leading zeros. |
lookup_bic | Look up a BIC/SWIFT Bank Identifier Code through published Graph data and rights checks. |
Help
Find guidance, answers to common questions, or contact the Aurato team.