AgentsReady
Verified deep dive · Payments

PayPal

Run the agent liveReport a change
8 minTime to key
NoNo-human path
4Human gates
7/10Onboarding score
CAPTCHAEmail verificationKYC / business checkPhone OTP

Fastest path to a key

  1. Phone OTP
    create a PayPal account (or log in) at developer.paypal.com - email + password, email confirmation; PayPal typically also verifies a phone number
  2. Developer Dashboard > Apps & Credentials (Sandbox): a Default Application already exists
  3. copy sandbox client_id + client_secret
  4. POST api-m.sandbox.paypal.com/v1/oauth2/token with client_credentials to get an access token (agent can do this)
  5. KYC / business check
    live: PayPal Business account required (business verification); US-only testing on a personal developer account
  6. Working API key

Biggest gap

Local MCP needs a raw OAuth access token that expires (~hours), forcing manual refresh; no CLI/device login.

Worth copying

Separate sandbox MCP host (mcp.sandbox.paypal.com) so agents can be pointed at test data by URL alone.

Sources (8) · checked 2026-10-11
69Readiness score / 100
L3 Agent-operableBeats 89% of 1,846 companies
Access20/20
Context11/20
Interfaces24/32
Onboarding14/19
Trust0/9
llms.txt · root
MCP · https://mcp.paypal.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. +6 Docs available as markdown. Serve every docs page as .md, or honour Accept: text/markdown.
  3. +5 Self-serve API keys. Show how to create a key on the first docs page. No sales call.
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
  • FAILDocs 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
  • FAILSelf-serve API keys5
  • PASSFree tier or test mode3
  • FAILAgent manifests4
  • FAILsecurity.txt2
  • FAILPublic status page3

Your fix pack: 8 changes, up to +31 points

Each change is ready to paste, filled in for paypal.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://paypal.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://paypal.com/openapi.json | head -c 200

Add the badge to your README

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