AgentsReady
Verified deep dive · Payments

Plaid

Run the agent liveReport a change
6 minTime to key
NoNo-human path
4Human gates
8/10Onboarding score
Email verificationKYC / business checkManual reviewTalk to sales

Fastest path to a key

  1. brew install plaid/plaid-cli/plaid
  2. Email verification
    `plaid register` opens Dashboard signup in browser (email, company info) -> verify email
  3. `plaid login` browser auth; CLI stores tokens and fetches Sandbox client_id + secret automatically
  4. call Sandbox (e.g. /sandbox/public_token/create, test creds user_good/pass_good)
  5. Manual review
    real data: `plaid trial` application form (US/CA, free, 10 Items) -> approval -> `plaid keys fetch`; full Production needs company profile + security questionnaire
  6. Working API key

Biggest gap

The remote MCP only works for Production-approved teams, so the zero-to-MCP path for a new developer is local-only.

Worth copying

CLI `login` that pulls API keys into local config so the agent never handles copy-pasted secrets, with explicit agent-mode (--json, stderr diagnostics, exit codes).

Sources (8) · checked 2026-10-11
79Readiness score / 100
L3 Agent-operableBeats 94% of 1,846 companies
Access20/20
Context17/20
Interfaces24/32
Onboarding16/19
Trust2/9
llms.txt · root
MCP · https://mcp.plaid.com/mcp

Biggest gains

  1. +8 Machine-readable API spec. Publish an OpenAPI spec at a stable URL like /openapi.json and link it from llms.txt.
  2. +4 Agent manifests. Publish an MCP server card (/.well-known/mcp.json) or A2A agent card.
  3. +3 llms-full.txt exists. Publish /llms-full.txt with the whole docs corpus in one file.
All 20 checks
  • PASSAgents get the real page, not a bot wall10
  • PASSrobots.txt lets user-triggered agents in6
  • PASSContent is server-rendered4
  • PASSllms.txt exists8
  • FAILllms-full.txt exists3
  • PASSDocs available as markdown6
  • PASSSitemap2
  • PASSStructured metadata1
  • PASSPublic developer docs4
  • FAILMachine-readable API spec8
  • PASSRemote MCP server for the product12
  • PASSDocs MCP or searchable docs4
  • PASSSDKs and a CLI4
  • PASSOAuth discovery metadata5
  • PASSAgents can self-register OAuth clients6
  • PASSSelf-serve API keys5
  • FAILFree tier or test mode3
  • FAILAgent manifests4
  • PASSsecurity.txt2
  • FAILPublic status page3

Your fix pack: 6 changes, up to +21 points

Each change is ready to paste, filled in for plaid.com, with a command to check it worked. Or hand the whole list to your coding agent.

An OpenAPI spec is the contract agents and SDK generators build against. Without it they guess from prose.

Where: https://plaid.com/openapi.json, linked from llms.txt and the API reference
// Serve the spec your API framework already generates (FastAPI: /openapi.json is built in).
// Next.js: app/openapi.json/route.ts
import spec from "@/openapi/openapi.json";
export const GET = () => Response.json(spec, { headers: { "Access-Control-Allow-Origin": "*" } });

// Every operation needs: operationId, summary, description, request/response examples,
// and the auth scheme (components.securitySchemes) so agents know how to send the key.
Check it worked:curl -s https://plaid.com/openapi.json | head -c 200

Add the badge to your README

AgentsReady badge for plaid.com
[![AgentsReady](https://agentsready.dev/badge/plaid.com)](https://agentsready.dev/c/plaid.com)