How Lithic’s scores are calculated
The full audit trail, recomputed from the verdict data at build time through the same code that produced the leaderboard: verdict × quality × story weight per cell, cells sum to dimension scores, dimensions blend into the PA Score. Every number on the product page is reproducible from this page alone; for why the formula looks like this, see the methodology.
verdict factors: full ×1.0 · partial ×0.6 · disputed ×0.3 · none ×0.0 · n/a excluded from both sides · cell points = weight × quality × factor · cell max = weight × 10
PA Score31/100
Agent-ready 51.8 × 0.30 = 15.54
API quality 18.3 × 0.20 = 3.66
Openness 14.4 × 0.20 = 2.88
Built-in AI 23.6 × 0.15 = 3.54
Automation 35.0 × 0.15 = 5.25
(15.54 + 3.66 + 2.88 + 3.54 + 5.25) ÷ (0.30 + 0.20 + 0.20 + 0.15 + 0.15) = 30.87 ÷ 1.00 = 30.9
Scores are stored to 1 decimal; the product page’s pills round to whole numbers for display. Each dimension below shows the stories, verdicts, and cited evidence behind its number.
Agent-ready51.8/100×0.30 of the PA blend
Outside-in: can YOUR agent reach and drive this product — API, MCP, CLI, headless runs, agent docs.
Point an agent at llms.txt or agent-oriented docsweight 2
2 (weight) × 8 (quality) × 1.0 (full) = 16.0 of 20 max
- [probe] https://docs.lithic.com/llms.txt“PROBE llms.txt: HTTP 200 at https://docs.lithic.com/llms.txt # Lithic Developer Documentation Documentation > The Lithic developer API provides a predictable and programmatic inter”
- [claimed-docs] https://docs.lithic.com/docs/mcp.md“Once connected, your AI assistant can search Lithic documentation, inspect endpoint schemas, generate integration code, and execute live API requests, all from within your editor.”
- [probe] https://docs.lithic.com/docs/mcp“official MCP server documented at https://docs.lithic.com/docs/mcp”
Run the product headlessly / in CI for automationweight 2
2 (weight) × 5 (quality) × 0.6 (partial) = 6.0 of 20 max
- [claimed-docs] https://docs.lithic.com/docs/simulating-transactions.md“The sandbox environment has additional endpoints to simulate transaction events originating from a merchant acquirer.”
- [claimed-docs] https://docs.lithic.com/docs/api-versioning.md“Send the `api-version` request header with the version you want”
- [probe] https://docs.lithic.com/llms.txt“PROBE llms.txt: HTTP 200 at https://docs.lithic.com/llms.txt # Lithic Developer Documentation Documentation > The Lithic developer API provides a predictable and programmatic inter”
Plug MCP servers into this product so it can use their toolsweight 3
n/a — not applicable to this product: excluded from numerator and denominator
- [claimed-docs] https://docs.lithic.com/docs/mcp.md“Once connected, your AI assistant can search Lithic documentation, inspect endpoint schemas, generate integration code, and execute live API requests, all from within your editor.”
- [probe] https://docs.lithic.com/docs/mcp“official MCP server documented at https://docs.lithic.com/docs/mcp”
Connect an agent via an official MCP serverweight 3
3 (weight) × 8 (quality) × 1.0 (full) = 24.0 of 30 max
- [claimed-docs] https://docs.lithic.com/docs/mcp.md“Once connected, your AI assistant can search Lithic documentation, inspect endpoint schemas, generate integration code, and execute live API requests, all from within your editor.”
- [probe] https://docs.lithic.com/docs/mcp“official MCP server documented at https://docs.lithic.com/docs/mcp”
- [claimed-docs] https://lithic.com/blog/mcp-server-agentic-payments“Create a virtual card and assign it to a test account... Configure Authorization Rules controlling merchant categories, transaction limits, and velocity... Run transactions against those rules”
Use an official CLIweight 2
2 (weight) × 0 (quality) × 0.0 (none) = 0.0 of 20 max
no evidence cited — the verdict rests on absence of evidence, re-checked on refresh
Drive the product through a documented public APIweight 3
3 (weight) × 8 (quality) × 1.0 (full) = 24.0 of 30 max
- [claimed-docs] https://docs.lithic.com/docs/auth-stream-access-asa.md“ASA requests are delivered as an HTTP POST request during authorization. The request body includes transaction metadata... Your endpoint should respond with HTTP status 200 and the approval decision”
- [claimed-docs] https://docs.lithic.com/docs/events-api.md“you can register and manage webhook URLs, replay webhook messages, control event subscription secrets, and search past events”
- [claimed-docs] https://docs.lithic.com/docs/api-versioning.md“Send the `api-version` request header with the version you want”
- [claimed-docs] https://docs.lithic.com/reference/postcards“Create a new virtual or physical card. Parameters `shipping_address` and `product_id` only apply to physical cards.”
- [claimed-docs] https://docs.lithic.com/docs/disputes-api.md“Lithic can help power your cardholders' disputes by handling networking filing for chargebacks and representment responses.”
- [claimed-docs] https://docs.lithic.com/docs/spend-limits.md“Lithic's Card and Account Spend Limits provide basic controls that help customers manage spend velocity.”
- [probe] https://docs.lithic.com/llms.txt“PROBE llms.txt: HTTP 200 at https://docs.lithic.com/llms.txt # Lithic Developer Documentation Documentation > The Lithic developer API provides a predictable and programmatic inter”
- [probe] https://docs.lithic.com/openapi.json“PROBE openapi: all candidate paths 404 (https://docs.lithic.com/openapi.json, https://docs.lithic.com/swagger.json, https://docs.lithic.com/api/openapi.json, https://docs.lithic.com/.well-known/openapi.json)”
Issue scoped/least-privilege API credentials for an agentweight 2
2 (weight) × 6 (quality) × 0.6 (partial) = 7.2 of 20 max
- [claimed-docs] https://docs.lithic.com/docs/authorization-rules-v2.md“Rules can be applied at three entity levels: Program level: across the entire card program, Account level: to specific accounts, Card level: to specific cards”
- [claimed-docs] https://docs.lithic.com/docs/authorization-rules-v2.md“shadow mode lets draft rules observe the authorization stream without affecting outcomes, while performance reports and backtesting measure impact over time”
- [claimed-docs] https://docs.lithic.com/reference/postcards“Create a new virtual or physical card. Parameters `shipping_address` and `product_id` only apply to physical cards.”
- [claimed-docs] https://lithic.com/blog/mcp-server-agentic-payments“Create a virtual card and assign it to a test account... Configure Authorization Rules controlling merchant categories, transaction limits, and velocity... Run transactions against those rules”
- [claimed-docs] https://lithic.com/solutions/agentic-commerce“Make the leap from insights to action with secure and autonomous issuing, payments, and controls for AI-powered workflows.”
- [claimed-docs] https://docs.lithic.com/docs/spend-limits.md“Lithic's Card and Account Spend Limits provide basic controls that help customers manage spend velocity.”
Build against official SDKsweight 2
2 (weight) × 0 (quality) × 0.0 (none) = 0.0 of 20 max
no evidence cited — the verdict rests on absence of evidence, re-checked on refresh
Subscribe to events via webhooksweight 2
2 (weight) × 8 (quality) × 1.0 (full) = 16.0 of 20 max
- [claimed-docs] https://docs.lithic.com/docs/events-api.md“you can register and manage webhook URLs, replay webhook messages, control event subscription secrets, and search past events”
- [claimed-docs] https://docs.lithic.com/docs/auth-stream-access-asa.md“ASA requests are delivered as an HTTP POST request during authorization. The request body includes transaction metadata... Your endpoint should respond with HTTP status 200 and the approval decision”
Agent-ready = 93.2 ÷ 180 × 100 = 51.8
API quality18.3/100×0.20 of the PA blend
The programmable surface once an agent is there — machine-readable spec, interactive docs, sandbox, versioning discipline.
Explore an interactive API reference with runnable examplesweight 2
2 (weight) × 0 (quality) × 0.0 (none) = 0.0 of 20 max
- [claimed-docs] https://docs.lithic.com/reference/postcards“Create a new virtual or physical card. Parameters `shipping_address` and `product_id` only apply to physical cards.”
- [probe] https://docs.lithic.com/openapi.json“PROBE openapi: all candidate paths 404 (https://docs.lithic.com/openapi.json, https://docs.lithic.com/swagger.json, https://docs.lithic.com/api/openapi.json, https://docs.lithic.com/.well-known/openapi.json)”
Download a machine-readable API spec (OpenAPI or equivalent)weight 2
2 (weight) × 0 (quality) × 0.0 (none) = 0.0 of 20 max
- [probe] https://docs.lithic.com/openapi.json“PROBE openapi: all candidate paths 404 (https://docs.lithic.com/openapi.json, https://docs.lithic.com/swagger.json, https://docs.lithic.com/api/openapi.json, https://docs.lithic.com/.well-known/openapi.json)”
- [probe] https://docs.lithic.com/llms.txt“PROBE llms.txt: HTTP 200 at https://docs.lithic.com/llms.txt # Lithic Developer Documentation Documentation > The Lithic developer API provides a predictable and programmatic inter”
Test against a sandbox environment without touching production dataweight 1
1 (weight) × 8 (quality) × 1.0 (full) = 8.0 of 10 max
- [claimed-docs] https://docs.lithic.com/docs/simulating-transactions.md“The sandbox environment has additional endpoints to simulate transaction events originating from a merchant acquirer.”
- [claimed-docs] https://lithic.com/blog/mcp-server-agentic-payments“Create a virtual card and assign it to a test account... Configure Authorization Rules controlling merchant categories, transaction limits, and velocity... Run transactions against those rules”
Rely on versioned APIs with a documented deprecation policyweight 2
2 (weight) × 4 (quality) × 0.6 (partial) = 4.8 of 20 max
- [claimed-docs] https://docs.lithic.com/docs/api-versioning.md“Send the `api-version` request header with the version you want”
API quality = 12.8 ÷ 70 × 100 = 18.3
Openness14.4/100×0.20 of the PA blend
Can you leave, inspect, or self-host — data export, open source, portability.
Do everything through the API that I can do in the UIweight 2
2 (weight) × 6 (quality) × 0.6 (partial) = 7.2 of 20 max
- [claimed-docs] https://docs.lithic.com/docs/authorization-rules-v2.md“Rules can be applied at three entity levels: Program level: across the entire card program, Account level: to specific accounts, Card level: to specific cards”
- [claimed-docs] https://docs.lithic.com/docs/authorization-rules-v2.md“shadow mode lets draft rules observe the authorization stream without affecting outcomes, while performance reports and backtesting measure impact over time”
- [claimed-docs] https://docs.lithic.com/docs/account-holders-kyc.md“KYC_BYO allows an API user to bypass the Lithic KYC process and create an individual account (available only to users with KYC processes pre-approved by Lithic)”
- [claimed-docs] https://docs.lithic.com/reference/postcards“Create a new virtual or physical card. Parameters `shipping_address` and `product_id` only apply to physical cards.”
- [claimed-docs] https://docs.lithic.com/docs/events-api.md“you can register and manage webhook URLs, replay webhook messages, control event subscription secrets, and search past events”
- [claimed-docs] https://docs.lithic.com/docs/simulating-transactions.md“The sandbox environment has additional endpoints to simulate transaction events originating from a merchant acquirer.”
- [probe] https://docs.lithic.com/docs/mcp“official MCP server documented at https://docs.lithic.com/docs/mcp”
- [probe] https://docs.lithic.com/openapi.json“PROBE openapi: all candidate paths 404 (https://docs.lithic.com/openapi.json, https://docs.lithic.com/swagger.json, https://docs.lithic.com/api/openapi.json, https://docs.lithic.com/.well-known/openapi.json)”
Export all of my data in open formats and leaveweight 3
3 (weight) × 0 (quality) × 0.0 (none) = 0.0 of 30 max
no evidence cited — the verdict rests on absence of evidence, re-checked on refresh
Read the product's source under an open licenseweight 2
n/a — not applicable to this product: excluded from numerator and denominator
no evidence cited — the verdict rests on absence of evidence, re-checked on refresh
Self-host the core productweight 3
n/a — not applicable to this product: excluded from numerator and denominator
no evidence cited — the verdict rests on absence of evidence, re-checked on refresh
Openness = 7.2 ÷ 50 × 100 = 14.4
Built-in AI23.6/100×0.15 of the PA blend
Inside-out: how agentic the product itself is for its users — built-in assistants, autonomous features.
Get AI-generated insights and suggestions from my data inside the productweight 2
2 (weight) × 0 (quality) × 0.0 (none) = 0.0 of 20 max
no evidence cited — the verdict rests on absence of evidence, re-checked on refresh
Set up automations that run autonomously in the backgroundweight 2
2 (weight) × 6 (quality) × 0.6 (partial) = 7.2 of 20 max
- [claimed-docs] https://docs.lithic.com/docs/auth-stream-access-asa.md“ASA requests are delivered as an HTTP POST request during authorization. The request body includes transaction metadata... Your endpoint should respond with HTTP status 200 and the approval decision”
- [claimed-docs] https://docs.lithic.com/docs/authorization-rules-v2.md“Rules can be applied at three entity levels: Program level: across the entire card program, Account level: to specific accounts, Card level: to specific cards”
- [claimed-docs] https://docs.lithic.com/docs/authorization-rules-v2.md“shadow mode lets draft rules observe the authorization stream without affecting outcomes, while performance reports and backtesting measure impact over time”
- [claimed-docs] https://docs.lithic.com/docs/events-api.md“you can register and manage webhook URLs, replay webhook messages, control event subscription secrets, and search past events”
- [claimed-docs] https://lithic.com/blog/mcp-server-agentic-payments“Create a virtual card and assign it to a test account... Configure Authorization Rules controlling merchant categories, transaction limits, and velocity... Run transactions against those rules”
- [claimed-docs] https://lithic.com/solutions/agentic-commerce“Make the leap from insights to action with secure and autonomous issuing, payments, and controls for AI-powered workflows.”
Delegate tasks to a built-in AI assistant inside the productweight 3
3 (weight) × 0 (quality) × 0.0 (none) = 0.0 of 30 max
- [claimed-docs] https://docs.lithic.com/docs/mcp.md“Once connected, your AI assistant can search Lithic documentation, inspect endpoint schemas, generate integration code, and execute live API requests, all from within your editor.”
- [probe] https://docs.lithic.com/docs/mcp“official MCP server documented at https://docs.lithic.com/docs/mcp”
- [claimed-docs] https://lithic.com/blog/mcp-server-agentic-payments“Create a virtual card and assign it to a test account... Configure Authorization Rules controlling merchant categories, transaction limits, and velocity... Run transactions against those rules”
Operate the product with natural-language commandsweight 2
2 (weight) × 7 (quality) × 1.0 (full) = 14.0 of 20 max
- [claimed-docs] https://docs.lithic.com/docs/mcp.md“Once connected, your AI assistant can search Lithic documentation, inspect endpoint schemas, generate integration code, and execute live API requests, all from within your editor.”
- [claimed-docs] https://lithic.com/blog/mcp-server-agentic-payments“Create a virtual card and assign it to a test account... Configure Authorization Rules controlling merchant categories, transaction limits, and velocity... Run transactions against those rules”
- [probe] https://docs.lithic.com/docs/mcp“official MCP server documented at https://docs.lithic.com/docs/mcp”
- [claimed-docs] https://lithic.com/solutions/agentic-commerce“Make the leap from insights to action with secure and autonomous issuing, payments, and controls for AI-powered workflows.”
Built-in AI = 21.2 ÷ 90 × 100 = 23.6
Automation35.0/100×0.15 of the PA blend
Depth of automation primitives — rules, scheduling, bulk operations, webhooks.
Perform bulk operations across many items at onceweight 2
2 (weight) × 0 (quality) × 0.0 (none) = 0.0 of 20 max
no evidence cited — the verdict rests on absence of evidence, re-checked on refresh
Define rules that trigger actions automatically on eventsweight 3
3 (weight) × 7 (quality) × 1.0 (full) = 21.0 of 30 max
- [claimed-docs] https://docs.lithic.com/docs/authorization-rules-v2.md“Rules can be applied at three entity levels: Program level: across the entire card program, Account level: to specific accounts, Card level: to specific cards”
- [claimed-docs] https://docs.lithic.com/docs/authorization-rules-v2.md“shadow mode lets draft rules observe the authorization stream without affecting outcomes, while performance reports and backtesting measure impact over time”
- [claimed-docs] https://docs.lithic.com/docs/spend-limits.md“Lithic's Card and Account Spend Limits provide basic controls that help customers manage spend velocity.”
- [claimed-docs] https://docs.lithic.com/docs/events-api.md“you can register and manage webhook URLs, replay webhook messages, control event subscription secrets, and search past events”
- [claimed-docs] https://docs.lithic.com/docs/auth-stream-access-asa.md“ASA requests are delivered as an HTTP POST request during authorization. The request body includes transaction metadata... Your endpoint should respond with HTTP status 200 and the approval decision”
Schedule recurring jobs or workflowsweight 2
n/a — not applicable to this product: excluded from numerator and denominator
no evidence cited — the verdict rests on absence of evidence, re-checked on refresh
Version, review, and roll back my automationsweight 1
1 (weight) × 0 (quality) × 0.0 (none) = 0.0 of 10 max
- [claimed-docs] https://docs.lithic.com/docs/authorization-rules-v2.md“shadow mode lets draft rules observe the authorization stream without affecting outcomes, while performance reports and backtesting measure impact over time”
Automation = 21.0 ÷ 60 × 100 = 35.0