Is dLocal agent-ready?

dLocal scores Band C on The Headless Index. Its JAIRF rating is not available because no machine-readable spec was scored. Its strongest area for agent use is API-first design intent; its weakest is MCP and agent posture.

Does dLocal publish an OpenAPI spec?

No published OpenAPI specification was found when dLocal was scored. That caps its JAIRF dimensions and forces agents to rely on documentation or reverse engineering to operate it.

What is dLocal's Headless Index score?

dLocal scores 56/100 on the Headless Index thesis-fit rubric and sits in Band C in the Payments category. The score weighs API-first design, headless operation, MCP and agent posture, schema observability, and webhooks.

03 / Scorecard / Payments

dLocal

Headless Index

56/100

JAIRF

N/A

Verified

AUG 20, 2026

Methodology v1 · JAIRF v1.0.0

dLocal earns Band C in the Payments category of The Headless Index, with a thesis-fit score of 56/100. Its strongest dimension is API-first design intent (14/20); its weakest scored dimension is MCP and agent posture (4/20). No public OpenAPI specification was found when dLocal was scored, which limits how far an agent can go without human integration work.

Editorial verdict

dLocal is partially headless and partly UI-led. The Headless Index thesis-fit score of 56/100 puts it mid-table on the index, and JAIRF is recorded as N/A for this vendor because no public OpenAPI specification was reachable for the open-source scorer. In practice, vendors at this tier are partly machine-consumable: the core flows are reachable through code but several adjacent surfaces still expect a human at a dashboard, and the rest of this verdict explains where dLocal lands inside that pattern. On the API surface, the question is whether the API is the product or a layer beneath the dashboard. dLocal is a cross-border payment platform focused on emerging markets, with a Payments API for collections and payouts. SDKs in Java, Python, Node, PHP, Ruby, and .NET. The API is the product; the merchant portal is for configuration and reporting.^[1] Schema observability is the related test: can an agent introspect the contract from cold, or does it have to read prose documentation to do so? REST documentation at docs.dlocal.com is detailed; OpenAPI references exist but a single canonical URL is not the headline artifact. Schema discovery requires docs context.^[2] An agent can drive parts of this product, but not all of it: integrators should plan for human-in-the-loop checkpoints where the headless surface stops short. On headless operability: Collections, payouts, refunds, chargebacks, and currency conversion are all programmable. The merchant portal handles country-specific configuration. The cross-border focus introduces more configuration that lives outside the API than tier-1 acquirers expose.^[3] On the MCP and agent-integration axis, which is the fastest-moving criterion in the index: No first-party dLocal MCP server. The product is operationally complex (country-specific payment methods, regulatory nuance) and not yet on the MCP integration curve.^[4] Event posture closes the loop: an agent that cannot react to state changes is reduced to polling. Webhook notifications cover payment status changes, payout updates, and chargebacks with HMAC signing. The catalog reflects the cross-border use case (currency conversion events, country-specific status codes). Net assessment: integrators can build agent flows against dLocal, but the rough edge to plan around is MCP posture^[5]. Expect to wrap missing pieces in bespoke glue or accept human-in-the-loop checkpoints. Workable but requires scaffolding.

Verdict by Headless Index pipeline (auto)

// AI-drafted from the evidence layer. Editorial review pending.

Scores

Scorecard detail

Headless Index · 5 sub-criteria

API-first design intent14/20

scored

dLocal is a cross-border payment platform focused on emerging markets, with a Payments API for collections and payouts. SDKs in Java, Python, Node, PHP, Ruby, and .NET. The API is the product; the merchant portal is for configuration and reporting.

signals (4)

+AI review appliedReviewer: Editorial review on 2026-05-20
−OpenAPI specNot found across 34 probe paths
−GraphQL endpointNot discovered (5 probes; project-scoped endpoints require a real project ID)
+SDKs maintained6 (kotlin, ruby, swift); top by stars: dlocal/dlocal-direct-ios-sdk (3 stars)

cite (1)

github.sdks@2026-05-19

Headless operation12/20

scored

Collections, payouts, refunds, chargebacks, and currency conversion are all programmable. The merchant portal handles country-specific configuration. The cross-border focus introduces more configuration that lives outside the API than tier-1 acquirers expose.

signals (9)

+AI review appliedReviewer: Editorial review on 2026-05-20
−API operations exposedNo OpenAPI spec; operations count unknown
·Docs pages crawled0 pages (crawler: none)
·Auth schemes documentedAuth documentation page not reached by crawler
·Setup / quickstart docsNot reached by crawler
·Billing docsNot reached by crawler
·Teams / org docsNot reached by crawler
·CLI docsNot reached by crawler
·Schema / data model docsNot reached by crawler

cite (1)

github.sdks@2026-05-19

MCP & agent posture4/20

scored

No first-party dLocal MCP server. The product is operationally complex (country-specific payment methods, regulatory nuance) and not yet on the MCP integration curve.

signals (4)

+AI review appliedReviewer: Editorial review on 2026-05-20
−Official MCP serverNone found in vendor's GitHub org or the official MCP registry
−Community MCP serversNone found
−Agent-friendly SDKsNo TypeScript/JavaScript SDK published (agents commonly run in TS/JS)

cite (1)

github.sdks@2026-05-19

Schema observability12/20

scored

REST documentation at docs.dlocal.com is detailed; OpenAPI references exist but a single canonical URL is not the headline artifact. Schema discovery requires docs context.

signals (3)

+AI review appliedReviewer: Editorial review on 2026-05-20
−OpenAPINot discovered across 34 standard probe paths
−GraphQL introspectionNo GraphQL endpoint discovered (5 probes; some vendors use project-scoped endpoints that require a real project handle)

cite (1)

github.sdks@2026-05-19

Webhooks & events14/20

scored

Webhook notifications cover payment status changes, payout updates, and chargebacks with HMAC signing. The catalog reflects the cross-border use case (currency conversion events, country-specific status codes).

signals (2)

+AI review appliedReviewer: Editorial review on 2026-05-20
·Webhook docs pageNot reached by crawler within budget (0 pages crawled). Cannot confirm whether vendor offers webhooks.

cite (1)

github.sdks@2026-05-19

JAIRF · 6 dimensions

JAIRF · N/A

This vendor does not publish a public OpenAPI specification. JAIRF cannot be computed. The Headless Index score and editorial verdict carry the readiness assessment.

No public OpenAPI specification discovered during collection

Band rationale:C band: scores 40-75 range

04 / Embed

Show dLocal's score on your site.

Drop a live badge into your README, footer, or marketing page. It updates automatically when we re-score, and every embed is a dofollow link back here.

Get embed code

Peers in Payments

SpreedlyC

Headless Index 56/100

KlarnaC

Headless Index 56/100

AdyenC

Headless Index 56/100

See full Payments ranking →

FAQ

dLocal and agent readiness

Is dLocal agent-ready?: dLocal scores Band C on The Headless Index. Its JAIRF rating is not available because no machine-readable spec was scored. Its strongest area for agent use is API-first design intent; its weakest is MCP and agent posture.
Does dLocal publish an OpenAPI spec?: No published OpenAPI specification was found when dLocal was scored. That caps its JAIRF dimensions and forces agents to rely on documentation or reverse engineering to operate it.
What is dLocal's Headless Index score?: dLocal scores 56/100 on the Headless Index thesis-fit rubric and sits in Band C in the Payments category. The score weighs API-first design, headless operation, MCP and agent posture, schema observability, and webhooks.