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

Daily transfers, volume and coverage →

Geracao

x402 resource x402 REST

editalmd.com · editalmd.com · Other services

not indexed Provider site ↗

Acesso individual a 15 páginas, com geração incluída quando necessária.

Price per call 0.3 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

Observed inflows · last 30 days

No inflow observed in this window

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

Observed inflows by window for Geracao.
Window Observed Transfers
Last complete day (2026-10-29) — —
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-30 → 2026-10-29 Scanned: 30/30 days Sample: 0 days with a measurement First seen: never Last update: 2026-10-29

Daily history →. Observed transfers show value arriving at the payout address; they do not establish service revenue.

Blockchain wallets

Full addresses · public payment evidence

Receiving 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

All published receiving wallet addresses for Geracao.
NetworkFull wallet addressEvidence
base 0x7c22D10a957c62044d03dB5C0086f500Fc645a26 Shared address · activity cannot be assigned to this serviceFrom source record · source: payai

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 Other services
  • Send native 14,518 calls · 0.05 USDC per call —
  • Submit 3,237 calls · 0.002 USDC per call —
  • Hash 503 calls · 0.002 USDC per call —
  • Horror Story API 467 calls · 0.01 USDC per call $4.61
  • Gas now 442 calls · 0.001 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 15,516 services in this category
With a measured call count 2,104 (13.6 %)
With a published price 3,454 (22.3 %)
With attributable inflows 87 (0.6 %)
Observed inflows · 30d $107.19
Median measured calls 2
Median price per call $0.01

Similar services

All of Other services →

Send native x402 REST usage

Pay the send-native execution fee (native coin transfer)

keyring-agent.blockchhub.link Other services 14,518 calls / 30d checked 2026-10-30
0.05 USDC per call per call

Submit x402 REST usage

Chainlink For Agents: submit a signed operation payload.

agents.chain.link Other services 3,237 calls / 30d checked 2026-10-30
0.002 USDC per call per call

Hash x402 REST usage

Compute a SHA-256, SHA-384, or SHA-512 digest of UTF-8 text; returns hexadecimal output (default SHA-256).

apex-edge-coral.vercel.app Other services 503 calls / 30d checked 2026-10-30
0.002 USDC per call per call

Horror Story API x402 REST usage

Access the exclusive horror story collection (pay-per-read).

horrorstoryapi.vercel.app Other services 467 calls / 30d checked 2026-10-30
0.01 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
Payment networks and amounts published for Geracao.
Network Scheme Amount Asset
base exact 0.3 USDC

“exact” is the price per call. “upto” is a ceiling the client sets, not a price. Atomic amount 300000 = 0.3 USDC per call on base.

What you can call

access: payment per call (x402)

endpoint https://editalmd.com/api/documento/9927611/geracao

Request

{
    "body": {
        "cotacao": []
    },
    "type": "http",
    "method": "POST",
    "bodyType": "json"
}

Response

{
    "type": "json",
    "example": {
        "type": "json",
        "schema": {
            "type": "object",
            "properties": {
                "error": {
                    "type": "string",
                    "description": "`geracao_necessaria`, `extracao_em_andamento`, `geracao_falhou` ou causa da indisponibilidade."
                },
                "acesso": {
                    "type": "object",
                    "description": "Ap\u00f3s pagamento confirmado: codigo privado e header X-Editalmd-Acesso. Guarde para vincular a uma conta ou reabrir enquanto an\u00f4nimo. Ap\u00f3s v\u00ednculo use sess\u00e3o da conta. N\u00e3o publique, n\u00e3o abre outro documento."
                },
                "status": {
                    "type": "string",
                    "description": "`pronto` quando a leitura pode ser aberta."
                },
                "cotacao": {
                    "type": "object",
                    "description": "P\u00e1ginas confirmadas pelo Licita\u00e7\u00e3o: paginas, source_sha256, preco_pagina_usd e preco_total_usd. Nulo quando n\u00e3o \u00e9 poss\u00edvel cotar."
                },
                "pagamento": {
                    "type": "object",
                    "description": "Quando cobrado: `recibo` da porta x402/cr\u00e9dito e `preco_usd`. Conserve mesmo se a origem falhar."
                },
                "processing": {
                    "type": "object",
                    "description": "Progresso real: `progress.stage` (preparing, reading, verifying, packaging), `pages_total`, `pages_processed`, `pages_completed`, `pass`; `updated_at` e `elapsed_ms`."
                },
                "geracao_url": {
                    "type": "string",
                    "description": "GET para estado/cota\u00e7\u00e3o; POST para comprar acesso individual."
                },
                "documento_id": {
                    "type": "integer",
                    "description": "Documento solicitado."
                },
                "markdown_url": {
                    "type": "string",
                    "description": "GET do Markdown, com o acesso comprado."
                },
                "retry_after_s": {
                    "type": "integer",
                    "description": "Intervalo m\u00ednimo at\u00e9 o pr\u00f3ximo GET de acompanhamento."
                },
                "acesso_comprado": {
                    "type": "object",
                    "description": "Esta credencial pode ler o documento, independentemente do estado global do texto."
                },
                "preco_pagina_usd": {
                    "type": "string",
                    "description": "US$ 0,02 por p\u00e1gina no site e API (x402 ou cr\u00e9dito)."
                }
            }
        }
    }
}

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

Opportunity insights

2 findings from measured data
  • Payment attribution is blocked

    The payout address is shared with 46 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

    87 of 15,516 services (0.6%) in Other services have attributable inflows; 2,104 have a source-measured call count. Median measured calls: 2.

    Rank this category by observed inflows →

What the provider says

Acesso individual a 15 páginas, com geração incluída quando necessária.

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


Facts and where they come from

Price
0.3 USDC per call Provider claim
Recorded value: 0.3 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 46 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 46 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
0x7c22D10a957c62044d03dB5C0086f500Fc645a26
0.3 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://editalmd.com/api/documento/9927611/geracao
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 0x7c22D10a957c62044d03dB5C0086f500Fc645a26
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.3 USDC per call
Evidence

Atomic amount 300000 = 0.3 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 1, Typ http).

facilitator.payai.network 2026-10-29
Provider Provider claim
editalmd.com
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.