MARKET MONITOR / CATALOGUE Services 131,105 MCP listed 40,658 x402 90,514 Rails Base / Solana / Polygon / Arbitrum Imported 2026-10-29 · 3 sources
← All services

Daily transfers, volume and coverage →

deliverability

x402 resource x402 REST

sigtap-outreach-api.sigtap.workers.dev · sigtap-outreach-api.sigtap.workers.dev · Comms & Messaging

Email deliverability check: SPF, DKIM, DMARC and MX record audit for a sending domain

Price per call 0.003 USDC per call published unit: per call
Calls · 30d — not reported by any source
Payers · 30d — not reported by any source
Observed inflows · 30d — not attributable
Inflow growth · 7d — not comparable (baseline under $1 or window incomplete)
Payment evidence Attribution blocked confidence: low · read 2026-10-29

Where you can pay

1 route from the provider's payment requirements
Payment networks and amounts published for deliverability.
Network Scheme Amount Asset
Base exact 0.003 USDC

“exact” is the price per call. “upto” is a ceiling the client sets, not a price. Atomic amount 3000 = 0.003 USDC per call on Base.

What you can call

access: payment per call (x402)

endpoint https://sigtap-outreach-api.sigtap.workers.dev/deliverability

Request

{
    "type": "http",
    "method": "GET",
    "queryParams": {
        "domain": "Sending domain to audit, e.g. openai.com"
    }
}

Response

{
    "type": "json",
    "example": {
        "spf": {
            "found": true,
            "issue": null,
            "record": "v=spf1 ...",
            "all_in_one": true
        },
        "dkim": [],
        "dmarc": {
            "found": true,
            "policy": "none"
        },
        "checks": [],
        "domain": "example.com",
        "verdict": "ready-to-send"
    }
}

Examples are the provider's own, not a call we made.

Observed inflows · last 30 days

No inflow observed in this window

The payout address is also published by 11 other service(s); the volume cannot be attributed to one of them.

Observed inflows by window for deliverability.
Window Observed Transfers
Last complete day (2026-10-28) — —
Last 7 days — —
Last 30 days — —
Growth, 7d against the 7 before not comparable
Source: on-chain transfer scan (USDC on Base) Window: 2026-09-29 → 2026-10-28 Scanned: 30/30 days Sample: 0 days with a transfer First seen: never Last update: 2026-10-28

Daily history → · what a transfer does and does not prove

Opportunity insights

2 findings from measured data
  • Payment attribution is blocked

    The payout address is shared with 11 other service(s). That is normal for facilitator and platform addresses, and it is why this profile shows no inflow figure. The volume exists — it just cannot be split without inventing a rule.

    How attribution works →
  • Category benchmark

    30 of 3,023 services (1.0%) in Comms & Messaging have attributable inflows; 888 have a source-measured call count. Median measured calls: 1.

    Rank this category by observed inflows →

What the provider says

Email deliverability check: SPF, DKIM, DMARC and MX record audit for a sending domain

Quoted from PayAI · source record · read 2026-10-29


Facts and where they come from

Price
0.003 USDC per call Provider claim
Recorded value: 0.003 USDC per call.
Unit
per call
Protocol
x402, REST · transport: HTTP Provider claim
Auth
x402
Source
PayAI · 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-26

Money, and what it actually proves

Verified revenue · 30d Unknown
Observed inflows · 30d —
Attribution Shared
Receipt ledger Not connected

Attribution blocked · confidence low
The payout address is also published by 11 other service(s); the volume cannot be attributed to one of them.

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 nothing measurable: no price, no attributable address, no receipt. The payout address is also published by 11 other service(s); the volume cannot be attributed to one of them.

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
0x963d450CA601d52B5D92a8540Aea8D4272223ae1
0.003 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. See evidence levels.

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://sigtap-outreach-api.sigtap.workers.dev/deliverability
Evidence

Als Resource-URL im Bazaar-Eintrag geführt.

facilitator.payai.network 2026-10-29
Input output Provider claim
Request/response examples published with the listing
Evidence

Beispiel-Ein- und -Ausgabe stammen aus dem Bazaar-Eintrag des Anbieters.

facilitator.payai.network 2026-10-29
Payment Provider claim
1 rail: Base · payee 0x963d450CA601d52B5D92a8540Aea8D4272223ae1
Evidence

Aus 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.

facilitator.payai.network 2026-10-29
Pricing Provider claim
0.003 USDC per call
Evidence

Atomic amount 3000 = 0.003 USDC per call on Base. Netzwerk: Base.

facilitator.payai.network 2026-10-29
Protocol Provider claim
x402 (HTTP 402 payment challenge)
Evidence

Im x402 Bazaar als zahlungspflichtige HTTP-Ressource gelistet (x402Version 2, Typ http).

facilitator.payai.network 2026-10-29
Provider Provider claim
sigtap-outreach-api.sigtap.workers.dev
Evidence

Die Ressource wird unter diesem Host im x402 Bazaar geführt; die Angaben stammen vom Anbieter.

facilitator.payai.network 2026-10-29

Endpoint checks

We have not called this endpoint yet. Until we do, everything above is what the source published — no more.

Tags


Competitors & category benchmark

Rank the whole category →
Closest competitors Comms & Messaging

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,023 services in this category
With a measured call count 888 (29.4 %)
With a published price 1,025 (33.9 %)
With attributable inflows 30 (1.0 %)
Observed inflows · 30d $52.88
Median measured calls 1
Median price per call $0.01

Similar services

All of Comms & Messaging →

Email x402 REST usage

Find email address for a person synchronously. Provide name + company or LinkedIn URL.

x402.orthogonal.com Comms & Messaging 2,674 calls / 30d checked 2026-10-29
0.03 USDC per call per call

DYOE Contact Extraction x402 REST usage

Extract public business emails, phone numbers, and social profiles from a website. Batch-safe contact enrichment for autonomous agents. Input: website URL. Returns structured JSON.

agents.dyoeway.org Comms & Messaging 831 calls / 30d checked 2026-10-29
0.01 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.

api.strale.io Comms & Messaging 596 calls / 30d checked 2026-10-29
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...

win.oneshotagent.com Comms & Messaging 541 calls / 30d checked 2026-10-29
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.