Email x402 REST usage
Find email address for a person synchronously. Provide name + company or LinkedIn URL.
0.03 USDC per call
per call
← All services
Daily transfers, volume and coverage →
Aura Agent Persistence
x402 resource x402 RESTaura.rohnelt.dev · aura.rohnelt.dev · Comms & Messaging
Give an autonomous agent what it structurally lacks: a real email address that receives verification codes, its own webhook URL, durable memory that survives between runs, and the ability to block on an event - an email, a webhook, a signal - without polling and without burning tokens while it waits
Price per call
1 USDC per call
published unit: per call
Calls · 30d
1
counted by the source, no daily split
Payers · 30d
1
distinct paying addresses seen by the source
Observed inflows · 30d
$2.00
2 transfers to the payout address
Inflow growth · 7d
—
not comparable (baseline under $1 or window incomplete)
Payment evidence
Observed transfers
confidence: medium
· read 2026-10-28
Observed inflows · last 30 days
$1.00USD observed / day
2026-10-01grey = not scanned · UTC days2026-10-30
| Window | Observed | Transfers |
|---|---|---|
| Last complete day (2026-10-30) | $0.00 | 0 |
| Last 7 days | $0.00 | 0 |
| Last 30 days | $2.00 | 2 |
| Growth, 7d against the 7 before | not comparable | |
Daily history →. Observed transfers show value arriving at the payout address; they do not establish service revenue.
Blockchain wallets
Full addresses · public payment evidenceReceiving wallets are payment addresses published for this service. Sending wallets transferred funds to an exclusive receiving address; this alone does not prove a purchase or identify an agent.
Receiving wallets · provider payment addresses
| Network | Full wallet address | Evidence |
|---|---|---|
| Base | 0xa61446444dae6c570813656ced71c18d68a5f0fd | Exclusive to this catalogue serviceFrom source record · source: x402_bazaar |
Sending wallets · observed counterparties
No sending wallet addresses have been retained for this service. Buyer wallets are unknown; daily totals and reported payer counts do not reveal their addresses.
Coverage includes retained scans only, not every historical transaction. Earlier daily totals cannot recover sender addresses. Sender lists exclude shared receiving wallets, whose transfers could belong to another service. A provider address does not establish wallet ownership.
Competitors & category benchmark
Rank the whole category →
Closest competitors
Comms & Messaging
- Email 2,674 calls · 0.03 USDC per call —
- Mx lookup 1,065 calls · 0.0216 USDC per call —
- Email validate 568 calls · 0.0324 USDC per call —
- Person profile 541 calls · 0.001 USDC per call —
- DYOE Contact Extraction 535 calls · 0.01 USDC per call —
Sorted by source-measured calls, not by our opinion. The right-hand figure is observed inflow, which stays empty for peers whose address is shared.
Category benchmark
3,050 services in this category
| With a measured call count | 907 (29.7 %) |
|---|---|
| With a published price | 1,051 (34.5 %) |
| With attributable inflows | 30 (1.0 %) |
| Observed inflows · 30d | $52.15 |
| Median measured calls | 1 |
| Median price per call | $0.01 |
Similar services
All of Comms & Messaging →Mx lookup x402 REST usage
Mail Server Lookup: Look up a domain's MX, A, AAAA, NS, TXT and SOA records, identify its email provider, and show its SPF and DMARC records.
0.0216 USDC per call
per call
Email validate x402 REST usage
Email Validation: Check email syntax, mail-server records, disposable domains, role addresses and likely typos. Returns checks without confirming a mailbox exists.
0.0324 USDC per call
per call
Person profile x402 REST usage
Profile enrichment from a name and company, an email, a phone or a profile URL. Phone lookup is off by default. include_phone=true adds the per-person add-on on the pricing page for up to one person; no phone hit is guar...
0.001 USDC per call
per call
Chosen by category and by whether we have measured them, not by who pays us. A sponsored placement in this list is labelled as such.
Service details, payment routes and source evidence
Where you can pay
1 route from the provider's payment requirements| Network | Scheme | Amount | Asset |
|---|---|---|---|
| Base | exact | 1 | USDC |
“exact” is the price per call. “upto” is a ceiling the client sets, not a price. Atomic amount 1000000 = 1 USDC per call on Base.
What you can call
access: payment per call (x402)endpoint
https://aura.rohnelt.dev/v1/credit/deposit/1
Request
{
"body": [],
"bodyType": "json",
"method": "POST",
"type": "http"
}
Response
{
"example": {
"balance_usd": "1.000000",
"credited_usd": "1.000000",
"next": "Use your bearer token on any /v1 operation."
},
"type": "json"
}
Examples are the provider's own, not a call we made.
Opportunity insights
2 findings from measured data-
Two independent sources agree
The observed inflow implies about 2 calls at list price; the source counted 1 (factor 2). A transfer is still not a purchase, but the order of magnitude holds — this is the strongest monetisation signal in the catalogue short of a receipt feed.
Peers with attributed inflows → -
Category benchmark
30 of 3,050 services (1.0%) in Comms & Messaging have attributable inflows; 907 have a source-measured call count. Median measured calls: 1.
Rank this category by observed inflows →
What the provider says
Give an autonomous agent what it structurally lacks: a real email address that receives verification codes, its own webhook URL, durable memory that survives between runs, and the ability to block on an event - an email, a webhook, a signal - without polling and without burning tokens while it waits, or to park its state, exit, and resume hours later exactly where it stopped. US$1.00 of prepaid credit, about 1,200 calls, debited off-chain.
Quoted from x402 Bazaar · source record · read 2026-10-28
Facts and where they come from
- Price
-
1 USDC per call
Provider claim
Recorded value: 1 USDC per call.
- Unit
- per call
- Protocol
- x402, REST · transport: HTTP Provider claim
- Auth
- x402
- Source
- x402 Bazaar (Coinbase CDP) · Public discovery API (provider-published records)
- Last checked
- Not checked by us yet — the data is as the source published it
- First seen
- 2026-10-24
- Usage
- 1 calls · 1 unique payers in the 30 days before 2026-10-24. Measured by the x402 Bazaar, not by us and not by the provider.
Money, and what it actually proves
Verified revenue · 30d
Unknown
Observed inflows · 30d
$2.00
Attribution
Exclusive
Receipt ledger
Not connected
Observed transfers
· confidence medium
Token transfers reached this service's own payout address. A transfer is not a purchase, and shared, refunded or unrelated transfers cannot be excluded.
Why revenue is “unknown”. A revenue figure needs a receipt: an amount a buyer actually paid for this service. We hold none for this entry, and we hold no funds at all. What we have instead is $2.00 arriving at the payout address in 30 days — that is volume, and a lower bound: transfers can be refunds, treasury moves, or payments for something else entirely.
Cross-check. At the published price the observed inflow would cover about 2 calls; the source counted 1. Two independent measurements of the same question — they never match exactly, because the effective price differs per call size and the address can also receive unrelated transfers.
Daily market statistics — the ledger view, day by day
No daily history has been archived for this service yet. Open the full daily history →
Payment rails
Base
· exact · USDC
0xa61446444dAE6c570813656CEd71C18D68A5f0Fd
1 USDC
From source record
A payment rail is where the provider asks to be paid. It is not proof that anything was paid through it.
Provenance
One row per statement. “Verified” means we checked it ourselves and the finding is quoted. “Provider claim” means we read it in the provider's own record. “Not found” is a statement about our search, not proof of absence.
| Statement | Status | What we found | Source | Checked |
|---|---|---|---|---|
| Endpoint | Provider claim |
https://aura.rohnelt.dev/v1/credit/deposit/1
EvidenceAls Resource-URL im Bazaar-Eintrag geführt. |
api.cdp.coinbase.com | 2026-10-28 |
| Input output | Provider claim |
Request/response examples published with the listing
EvidenceBeispiel-Ein- und -Ausgabe stammen aus dem Bazaar-Eintrag des Anbieters. |
api.cdp.coinbase.com | 2026-10-28 |
| Payment | Provider claim |
1 rail: Base · payee 0xa61446444dAE6c570813656CEd71C18D68A5f0Fd
EvidenceAus den `accepts`-Einträgen: Netzwerk, Asset, Empfängeradresse und Betrag. Die Adresse ist die Grundlage der späteren On-Chain-Zuordnung; sie ist noch nicht durch eine eigene 402-Antwort bestätigt. |
api.cdp.coinbase.com | 2026-10-28 |
| Pricing | Provider claim |
1 USDC per call
EvidenceAtomic amount 1000000 = 1 USDC per call on Base. Netzwerk: Base. |
api.cdp.coinbase.com | 2026-10-28 |
| Protocol | Provider claim |
x402 (HTTP 402 payment challenge)
EvidenceIm x402 Bazaar als zahlungspflichtige HTTP-Ressource gelistet (x402Version 2, Typ http). |
api.cdp.coinbase.com | 2026-10-28 |
| Provider | Provider claim |
aura.rohnelt.dev
EvidenceDie Ressource wird unter diesem Host im x402 Bazaar geführt; die Angaben stammen vom Anbieter. |
api.cdp.coinbase.com | 2026-10-28 |
| Usage | Verified |
1 calls / 1 unique payers in the last 30 days
EvidenceSource-reported usage from Coinbase x402 Bazaar, read on 2026-10-28. Letzter Aufruf laut Quelle: 2026-10-05T06:00:17.557Z. Aufrufe sind kein Umsatz. |
api.cdp.coinbase.com | 2026-10-28 |
Endpoint checks
We have not called this endpoint yet. Until we do, everything above is what the source published — no more.