NOTE: re-routing reply → article because source=other (AWS blog — no reply thread, email=null). product_fit=mnemopay, score=96 ≥ 85.

AWS just entered agent payments. here's what they got right — and what they punted on.

AWS shipped AgentCore Payments with Coinbase and Stripe last month. Fully managed wallet, session-level spending limits, autonomous agent transactions. If you're building agents that move money, this is the most important infrastructure announcement of the year.

But after working through the architecture, there's a gap they explicitly punted on: Agent FICO.

what AgentCore payments actually does

The setup is clean. You connect a wallet, set session-level spending limits per agent, and the agent can transact autonomously within those bounds. Coinbase handles crypto rails. Stripe handles traditional fiat. One managed layer on top.

Session limits are the key mechanism. Instead of an always-on API key that can drain a card, each agent session gets a capped budget. The agent can't spend past it.

That's a real improvement over "give the agent an API key and hope for the best."

what they punted on

Session limits cap the damage. They don't tell you whether this specific agent should be trusted with this specific transaction type.

There's no runtime creditworthiness signal. No score that reflects an agent's historical spend accuracy, refund rate, anomaly history, or whether it's ever hallucinated a payment into the wrong account. You set a session limit at deploy time and that's it.

The result: a brand-new agent with zero track record gets the same trust budget as a battle-tested agent with 10K successful transactions and a 0.2% error rate.

That's not how any other credit system works. And it's going to matter as agents get more autonomy.

what Agent FICO adds to this stack

Agent FICO is a 300–850 score for autonomous agents — computed from actual transaction history, refund/chargeback rates, spend consistency, and anomaly signals. It lives outside the wallet infrastructure (so it works with AgentCore, x402, MnemoPay, or anything else).

The practical difference: dynamic trust gates instead of static session budgets. A new agent starts at a conservative limit. An agent with 12 months of clean behavior and a 790 FICO earns a higher ceiling automatically. An agent that starts hallucinating payments gets its score cut and its limits tightened in real-time before it drains the budget.

v1.0.0-beta.1 is live on npm with 1.4K weekly downloads and 672 tests covering the scoring pipeline.

how they fit together

AgentCore Payments + Agent FICO is closer to a complete stack than either alone.

AgentCore gives you the rails — wallet, session budgets, Stripe/Coinbase integration. Agent FICO gives you the runtime trust layer — dynamic limits based on observed behavior rather than static configuration.

You can use MnemoPay's SDK alongside AgentCore's rails if you already have the AWS integration. The FICO scoring layer is transport-agnostic.

the move

If you're already on AgentCore, the session-limit architecture is sound. Add a creditworthiness signal before you put agents in production with real budget authority. Static limits set at deploy time won't hold up as agents accumulate transaction history — yours or someone else's.

Agent FICO SDK: https://mnemopay.com