passabsent from every registrycounted above 0% of Compute
0.25 USDC
per call, as the listing declares it on eip155:
Compare with anotherEvery figure as JSONCite this page
the price, as of 2026-10-13 14:08 UTC · method
- Validation state
- pass
- Uptime, 7 / 30 / 90 days
- 100% / 100% / 100%
- Calls, trailing 30 days
- 1
- Unique payers, trailing 30 days
- 1
- Last called
- 2026-09-26 03:09 UTC
- First observed by TOLLderived
- 2026-09-26
- Pricederived
- 0.25 USDC
- Networks
- 1
How big is this endpoint among the ones like it?
No trace is drawn of this endpoint’s own volume. Its counters have changed 1 time across 53 observations, and 3 changes are the fewest this site will draw a trace through, because two points and a guess are not a series. Every observation is in the JSON.
TOLL files process document execute under compute: a POST endpoint on www.tradepilotusa.com, listed in neither registry at the last pull.
process document execute is priced at 0.25 USDC on Base.
The request to process document execute is a json body with the fields brief, audience and source_text.
A response from process document execute, as declared, includes task, summary, artifact, provenance, request_id, assumptions and 2 others.
process document execute answered the sweep of 2026-10-30 with a valid 402, as at every sweep since 2026-09-26.
process document execute is the only listed endpoint on www.tradepilotusa.com.
In the trailing 30 days: one call, one payer.
process document execute was last called 37 days before the snapshot.
Closest in price to process document execute within compute: job token research at api.losbeto.xyz and openfunnel tech companies at vaaya.ai.
process document execute is near the top of prices in compute; 95% of comparable listings are cheaper.
The wallet paid by process document execute is the payee of 120 endpoints on one host.
process document execute was missing from the Coinbase registry at the pull of 2026-11-01, confirmed at the pull of 2026-11-01; that is registry presence, not liveness.
Where the sentences above compare this endpoint with others, the comparison is against the index as it stands now, live; the figures above are final.
the payment options, as of 2026-10-13 14:08 UTC · method
| registry | network | asset | amount | scheme | pay to |
|---|---|---|---|---|---|
| Coinbase | eip155: | USDC | 0.25 USDC | exact | 0x421b1e…d0a89e |
the checks, as of 2026-10-30 08:55 UTC · methodendpoint answered HTTP 402
No named check failed.
Every sweep that observed this endpoint, newest first.
| observed, UTC | state | failed checks | sweep |
|---|---|---|---|
| 2026-10-30 08:55 UTC | pass | 0 | daily-2026-10-30 |
| 2026-10-29 08:35 UTC | pass | 0 | daily-2026-10-29 |
| 2026-10-28 08:58 UTC | pass | 0 | daily-2026-10-28 |
| 2026-10-27 08:43 UTC | pass | 0 | daily-2026-10-27 |
| 2026-10-26 15:15 UTC | pass | 0 | daily-2026-10-26 |
| 2026-10-23 08:51 UTC | pass | 0 | daily-2026-10-23 |
| 2026-10-21 11:24 UTC | pass | 0 | daily-2026-10-21 |
| 2026-10-20 10:59 UTC | pass | 0 | daily-2026-10-20 |
| 2026-10-19 08:35 UTC | pass | 0 | daily-2026-10-19 |
| 2026-10-18 10:34 UTC | pass | 0 | daily-2026-10-18 |
| 2026-10-17 20:53 UTC | pass | 0 | daily-2026-10-17 |
| 2026-10-16 06:45 UTC | pass | 0 | daily-2026-10-16 |
| 2026-10-15 08:31 UTC | pass | 0 | daily-2026-10-15 |
| 2026-10-14 06:35 UTC | pass | 0 | daily-2026-10-14 |
| 2026-10-13 11:18 UTC | pass | 0 | daily-2026-10-13 |
| 2026-10-12 08:39 UTC | pass | 0 | daily-2026-10-12 |
| 2026-10-11 07:23 UTC | pass | 0 | daily-2026-10-11 |
| 2026-10-10 15:27 UTC | pass | 0 | daily-2026-10-10 |
| 2026-10-09 08:02 UTC | pass | 0 | daily-2026-10-09 |
| 2026-10-08 09:33 UTC | pass | 0 | daily-2026-10-08 |
| 2026-10-07 08:53 UTC | pass | 0 | daily-2026-10-07 |
| 2026-10-06 09:44 UTC | pass | 0 | daily-2026-10-06 |
| 2026-10-05 08:42 UTC | pass | 0 | daily-2026-10-05 |
| 2026-10-04 11:07 UTC | pass | 0 | daily-2026-10-04 |
| 2026-10-03 05:53 UTC | pass | 0 | daily-2026-10-03 |
| 2026-10-02 15:06 UTC | pass | 0 | daily-2026-10-02 |
| 2026-10-01 07:59 UTC | pass | 0 | daily-2026-10-01 |
| 2026-09-30 07:19 UTC | pass | 0 | daily-2026-09-30 |
| 2026-09-29 19:35 UTC | pass | 0 | daily-2026-09-29 |
| 2026-09-28 06:22 UTC | pass | 0 | daily-2026-09-28 |
| 2026-09-26 07:20 UTC | pass | 0 | new-after-daily-2026-09-26 |
Presence in a registry, not liveness of the service (method). Newest first.
- absence from Coinbase confirmed, rule v1
- absent from Coinbase at this pull
- listed in Coinbase
From the registry record, not validated by TOLL.the declared schema, as of 2026-09-26 03:09 UTC · method
The input and output block
{
"input": {
"body": {
"brief": "Convert supplied process notes into steps, inputs, outputs, owners, exception paths, and handoffs. Use only the supplied fictional example material and clearly identify missing evidence.",
"audience": "Business operations manager",
"source_text": "Fictional supplied business brief: Example Door Company installs residential entry doors in Dallas with a two-person crew and weekday consultations. The project is to improve scheduling over six weeks. Vendor A proposes a process assessment for $500; Vendor B proposes an assessment and staff workshop for $800. Both prices are fictional examples, not researched market prices. Evaluation criteria are implementation effort, scope clarity and staff training. Current booking volume, customer feedback, vendor references and measured outcomes are unknown."
},
"type": "http",
"method": "POST",
"bodyType": "json"
},
"output": {
"type": "json",
"example": {
"task": "process_document",
"summary": "The draft outlines the residential door installation scheduling process in steps with defined inputs, outputs, owners, exception paths, and handoffs based solely on the supplied fictional example. It ",
"artifact": "Illustrative excerpt from a synthetic provider check:\n## Process Draft: Residential Entry Door Installation Scheduling Improvement\n\n### Steps\n1. **Initial Consultation Booking**\n - Schedule weekday consultations with customers.\n - Input: Customer contact information, preferred consultation date/time.\n - Output: Confirmed consultation appointment.\n - Owner: Scheduling Coordinator.\n - Exception Path: Customer unavailable on proposed dates; reschedule or escalate.\n - Handoff: Scheduling Coordinator to Consultation Crew.\n\n2. **Consultation ",
"provenance": {
"source": "buyer_supplied",
"generated_at": "2026-09-22T14:41:42.159Z",
"external_research_performed": false
},
"request_id": "example_process_document",
"assumptions": [
"The two-person crew conducts both consultations and installations.",
"Consultations and installations occur only on weekdays."
],
"evidence_gaps": [
"Current booking volume data to understand scheduling load.",
"Customer feedback data to assess satisfaction and identify pain points."
],
"requires_human_review": true
}
}
}Cite this page
This endpoint is delisted: the page is frozen at its last observation and its live URL is the stable one. Data reuse is under CC BY 4.0 (terms).
Plain text
TOLL, "process document execute on www.tradepilotusa.com". https://tollindex.com/e/www-tradepilotusa-com-api-agent-commerce-v1-services-process-document-execute-6fe155. Accessed [access date].
BibTeX
@misc{toll-e-www-tradepilotusa-com-api-agent-commerce-v1-services-process-document-execute-6fe155-2026-11-01,
author = {TOLL},
title = {process document execute on www.tradepilotusa.com},
howpublished = {\url{https://tollindex.com/e/www-tradepilotusa-com-api-agent-commerce-v1-services-process-document-execute-6fe155}},
year = {2026},
month = {11},
note = {Frozen at its last observation, 2026-11-01 21:59 UTC. Accessed [access date].}
}None yet. Anything submitted through the form below is published here with its outcome.