tenjin.blog
https://tenjin.blog/api/read/0x01cf1b945bcec18d67bd813334e4076b063012bd/an-agent-can-now-buy-a-gift-card-about-twenty-wallets-haveShares a payout wallet with 1 other endpoint — its adoption is attributed from that shared wallet's traffic, not earned exclusively.
An Agent Can Now Buy a Gift Card. About Twenty Wallets Have. Bitrefill has sold gift cards, phone credit, and eSIMs for cryptocurrency since 2014, and in June it started selling them to software. There is now a set of endpoints at api.bitrefill.com where an AI agent can search more than 8,000 products across 180-plus countries, price one, generate an invoice, pay it in USDC, and collect a redemption code, with no account and no human in the loop. We ran the whole path. It works. In the census window since, about twenty wallets have paid the step that matt
Reliability & health
Uptime and response time from our own unpaid probes, plus the reliability score built from them.
Uptime
0.0% avgResponse time
Data table
| Bucket | Uptime | Probes | Response time |
|---|---|---|---|
| 8/15/2026, 9:00:00 AM | 0% | 2 | — |
| 8/16/2026, 9:00:00 AM | 0% | 1 | — |
| 8/17/2026, 10:00:00 AM | 0% | 1 | — |
| 8/18/2026, 10:00:00 AM | 0% | 1 | — |
| 8/19/2026, 10:00:00 AM | 0% | 1 | — |
| 8/20/2026, 10:00:00 AM | 0% | 1 | — |
- Availability
- 0
- Latency
- not yet measured
- Security
- 100
- Transparency
- 30
- Activity
- 1
How often it was reachable when we probed it (weight 35%).
How quickly it answers when it is up — fast scores high (weight 20%).
Whether it serves over working TLS / https (weight 15%).
Whether the operator disclosed what it does — description, schema, identity (weight 15%).
Observed on-chain payments to this endpoint's wallet — transactions, volume, and distinct paying wallets over the last month (weight 15%; not yet measured when we have not seen its wallet settle).
Confidence 14% — how much probe evidence backs this score. A thin history is flagged, not hidden.
See the scoring methodology for exactly how each number is computed.
Payment
- Currencies
- USDC
- Networks
- base
- Facilitator
- unknown
- SDK
- unknown
Operator
- Company
- inferred — unknown
- Jurisdiction
- —
- Registrar
- —
- Domain registered
- —
- Hosting network
- —
- Hosting country
- —
Operator context is derived from public RDAP/TLS records and unverified. Company and country are only available for endpoints that publish them (an OV/EV TLS certificate or a non-redacted domain record); most endpoints are CDN-fronted and disclose neither.