Which card fits — before the agent pays
Declare · Enforce · Optimize
Banks don't do what we do. Cards can't do what we can.
Not a bank. Not an issuer. Not a lender.
An agent approaches pay or book. It declares which cards it may use and under what limits. We check the declaration, then — for partners — rank which eligible card (if any) fits this moment. Multi-issuer. Non-custodial. The money never passes through us.
For a deeper read: a weigh station for agents that spend — not a toll, and not a fine booth. Agent runtimes are the highway; they move the work. We sit beside them with the rulebook: which cards, which limits, which categories, when a human must approve. Eligible? It rolls with the card that fits. Not eligible? A clear no, with a reason. We never touch the freight and we never touch the money.
.fafa agent card standard.Open channel. Questions, suggestions, design partners, Pilot — email team@platinumcard.ai. Help guide what we build.
Public validation stores nothing and returns a verdict.
curl -X POST https://validate.platinumcard.ai \
-H 'content-type: application/json' \
-d '{"version":"0.1.1","cards":[]}'
The response shape is unstable and versioned 0.1.1. Every
response carries the disclaimer above. Declarations containing secret-like
fields — card numbers, API keys, bank details — are rejected, not stored.
A portfolio describes cards the way software should — as data. Tier and network are plain enumerated values, and every network is treated alike.
network: visa | mastercard | amex | discover | other product_tier: platinum | gold | infinite | signature | other
"Platinum" has been a generic industry tier descriptor since the American Express v. Visa / First USA litigation settled in 1996–97. This project uses it in exactly that sense — a product-tier value alongside gold, infinite and signature — and not as a reference to any issuer's product.