Can you trust the numbers in Agentcard?
Agentcard is a wallet for AI agents, so that agents can buy online what a person can buy. Its own help pages give 3 reasons its numbers can look different from what you expect. The first to rule out: As Agentcard's docs say, a transaction can be approved but not settled yet, so it may not have turned into spend that has finished.
Is it broken, or just counted differently?
A number can look wrong because the business changed, or because of how Agentcard counts it. Below is what Agentcard keeps, where its help pages say the numbers can differ, and how to check them yourself.
What does Agentcard keep track of?
Agentcard keeps a record of every purchase attempt made by an agent, whether on a card or paid from a Vault.
In Agentcard's own words:
A transaction is one purchase attempt: a charge on a card, or a checkout paid from a user's Vault.
Transactions overview, read 2026-11-12.Agentcard keeps a company balance showing how much is free to put on new cards.
In Agentcard's own words:
See what your company can spend on new cards.
Company wallet overview, read 2026-11-12.
What can make Agentcard's numbers look wrong?
As Agentcard's docs say, a transaction can be approved but not settled yet, so it may not have turned into spend that has finished.
In Agentcard's own words:
Approved, not settled yet.
Transactions overview, read 2026-11-12.As Agentcard's docs explain, the same event can be delivered more than once, so counting events without removing repeats can overstate them.
In Agentcard's own words:
Delivery is at least once, so deduplicate on `id`.
Webhooks overview, read 2026-11-12.As Agentcard's docs say, test and live transactions are read with different credentials, so numbers can differ depending on which one is used.
In Agentcard's own words:
Your credential decides the mode: sandbox credentials read sandbox transactions, production credentials read live ones.
Transactions overview, read 2026-11-12.
How do I check Agentcard's numbers myself?
An owner counting transactions should read every page of the list, because a single page may not hold them all.
In Agentcard's own words:
To read everything, keep passing the `cursor` from each page until `has_more` is `false`.
List transactions, read 2026-11-12.An owner can filter the list by time to count transactions for one period and compare it with their own records.
In Agentcard's own words:
Only transactions at or after this ISO 8601 time.
List transactions, read 2026-11-12.
How does Agentcard work with Feder?
Connect Agentcard to Feder and it joins your Money apps. Feder only reads. It never changes anything in Agentcard.
When you connect Agentcard, Feder checks the connection straight away and shows Connected only when that check passes. If a reading cannot be taken later, Feder shows it as not read, never as zero.
Other apps that feed Money
- Striperevenue
- PayPalrevenue
- WooCommercerevenue
- Rechargesubscription revenue
- Zohoinvoiced
- Wave Accountinginvoiced
Where do these answers come from?
Everything this page says about Agentcard comes from Agentcard's own pages, quoted above with the date we read them. Last reviewed 2026-11-12. We read them again by 2027-11-12. If one changes, this page changes or comes down.
Know the day a number breaks, not the month after.
Some numbers are too quiet to judge daily, such as a form filled in a few times a week. Until there is enough of your own history to judge a change, Feder says it is still learning and scores nothing, rather than guessing.