Exa x402 REST usage
Exa /search endpoint
Daily transfers, volume and coverage →
qf-api.quietforge-studio.workers.dev · qf-api.quietforge-studio.workers.dev · Search & Research
Detect the structure of a book manuscript before typesetting it: the chapter list our engine will use (numbered / unnumbered), words and scene breaks per chapter, paragraph count, characters the book font cannot print, and the warnings a full build would raise. Same parser as /v1/typeset, so what yo
The payout address is also published by 3 other service(s); the volume cannot be attributed to one of them.
| Window | Observed | Transfers |
|---|---|---|
| Last complete day (2026-10-31) | — | — |
| Last 7 days | — | — |
| Last 30 days | — | — |
| 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.
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.
| Network | Full wallet address | Evidence |
|---|---|---|
| Base | 0x3f5115236f25618c16021e983acaaf2caaa1a35e | Shared address · activity cannot be assigned to this serviceFrom source record · source: payai |
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.
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.
| With a measured call count | 10,601 (61.2 %) |
|---|---|
| With a published price | 11,105 (64.1 %) |
| With attributable inflows | 110 (0.6 %) |
| Observed inflows · 30d | $3,382.55 |
| Median measured calls | 2 |
| Median price per call | $0.01 |
Exa /search endpoint
Web search built for agents, served over Pocket Network: POST /v1/search with a query and an optional max_results, and get the results back as one JSON object. Results vary run to run, as web search does. GET /v1/version...
Search cached Seats.aero award availability by origin, destination, dates, cabin, carriers, and pagination.
Search Twitter/X tweets with advanced filters. Returns up to 20 tweets per page, most recent first, with pagination. At least one filter required. Params: words, phrase, anyWords, noneWords, hashtags, from, to, mentionin...
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.
| Network | Scheme | Amount | Asset |
|---|---|---|---|
| Base | exact | 0.01 | USDC |
“exact” is the price per call. “upto” is a ceiling the client sets, not a price. Atomic amount 10000 = 0.01 USDC per call on Base.
endpoint
https://qf-api.quietforge-studio.workers.dev/v1/typeset/outline
{
"body": {
"format": "txt",
"manuscript": "Chapter One\n\nThe lamp on the landing had burned all night, and by morning the hallway smelled faintly of paraffin and toast. Nora stood at the window with her coat already on, counting the carts that passed the gate. Six, then seven. The eighth was late, and she knew before it turned the corner that it would be empty.\n\n* * *\n\nHer brother came down at nine, still buttoning his cuffs, and asked whether the letter had arrived. It had not. She said so without turning round, and he took his tea to the study and shut the door.\n\nChapter Two\n\nThe letter came on Thursday, folded twice, and told them nothing they had not guessed. The field was sold. The buyer would take possession at Michaelmas, and the tenants could stay until then on the old terms. Nora read it aloud at the table, slowly, and when she finished nobody spoke for a long time.\n"
},
"type": "http",
"method": "POST",
"bodyType": "json"
}
{
"type": "json",
"example": {
"words": 150,
"chapters": [
{
"n": 1,
"title": "",
"words": 95,
"scenes": 1,
"numbered": true,
"sections": 0
},
{
"n": 2,
"title": "",
"words": 55,
"scenes": 0,
"numbered": true,
"sections": 0
}
],
"warnings": [
"Very short chapters (<150 words): (untitled), (untitled) \u2014 check they are real chapters."
],
"elapsed_ms": 114,
"paragraphs": 3,
"scene_breaks": 1,
"missing_glyphs": ""
}
}
Examples are the provider's own, not a call we made.
The payout address is shared with 3 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 →110 of 17,331 services (0.6%) in Search & Research have attributable inflows; 10,601 have a source-measured call count. Median measured calls: 2.
Rank this category by observed inflows →Detect the structure of a book manuscript before typesetting it: the chapter list our engine will use (numbered / unnumbered), words and scene breaks per chapter, paragraph count, characters the book font cannot print, and the warnings a full build would raise. Same parser as /v1/typeset, so what you see here is exactly how the book will be divided.
Quoted from PayAI · source record · read 2026-10-29
Attribution blocked
· confidence low
The payout address is also published by 3 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 3 other service(s); the volume cannot be attributed to one of them.
No daily history has been archived for this service yet. Open the full daily history →
A payment rail is where the provider asks to be paid. It is not proof that anything was paid through it.
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://qf-api.quietforge-studio.workers.dev/v1/typeset/outline
EvidenceAls Resource-URL im Bazaar-Eintrag geführt. |
facilitator.payai.network | 2026-10-29 |
| Input output | Provider claim |
Request/response examples published with the listing
EvidenceBeispiel-Ein- und -Ausgabe stammen aus dem Bazaar-Eintrag des Anbieters. |
facilitator.payai.network | 2026-10-29 |
| Payment | Provider claim |
1 rail: Base · payee 0x3F5115236f25618c16021E983acaAF2CAaa1A35e
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. |
facilitator.payai.network | 2026-10-29 |
| Pricing | Provider claim |
0.01 USDC per call
EvidenceAtomic amount 10000 = 0.01 USDC per call on Base. Netzwerk: Base. |
facilitator.payai.network | 2026-10-29 |
| Protocol | Provider claim |
x402 (HTTP 402 payment challenge)
EvidenceIm x402 Bazaar als zahlungspflichtige HTTP-Ressource gelistet (x402Version 2, Typ http). |
facilitator.payai.network | 2026-10-29 |
| Provider | Provider claim |
qf-api.quietforge-studio.workers.dev
EvidenceDie Ressource wird unter diesem Host im x402 Bazaar geführt; die Angaben stammen vom Anbieter. |
facilitator.payai.network | 2026-10-29 |
We have not called this endpoint yet. Until we do, everything above is what the source published — no more.