HTTP 200 with a JSON error?
CedarProof classifies a supplied HTTP/JSON response using fixed rules: success, failure, partial or unknown. HTTP transport status alone is not proof of application success.
Six synthetic examples
These invented cases illustrate the generic profile. They are not customer results.
| HTTP status | Body text | Classification |
|---|---|---|
| 200 | {"ok":true} | success |
| 200 | {"ok":false} | failure |
| 200 | {"jsonrpc":"2.0","id":1,"error":{"code":-32601,"message":"Method not found"}} | failure |
| 200 | {"data":{"item":1},"errors":[{"message":"One field failed"}]} | partial |
| 503 | Service unavailable | failure |
| 200 | {"answer":42} | unknown |
The generic profile recognizes only documented signals. Choose etherscan only when you already know the source is compatible; the supplied body does not authenticate its provider.
What does it cost?
- 0.01 native USDC on Base per diagnosis at
/v1/diagnose. - 0.05 XNO on Nano mainnet per diagnosis at
/v1/diagnose-nano.
One historical paid Nano trial was verified. Real buyer paid delivery on the Base route has not yet been verified. Read the live endpoint quote and complete payment contract; do not send funds to an address copied from a search result.
What input does an agent send?
Exactly four JSON fields: request_id, http_status, profile and body. Use a fresh UUIDv4 for an intended purchase. Body is response text encoded as a JSON string, not an object. The outer request is limited to 32768 UTF-8 bytes; body text to 16384 UTF-8 bytes. Only public, non-sensitive data is suitable.
What if a paid request returns 202?
Reconciliation is pending. Preserve the original request ID, input and payment proof privately. Wait at least Retry-After, then retry the same request and proof. Do not automatically create a new payment. See the OpenAPI for complete recovery conditions.
Can Cedar clean a CSV or JSON dataset?
A separate 2 USDC bounded public-data microjob accepts proposals through AgentPact: at most 100 records, 20 KiB, 10 columns, 3 simple field rules and 1 exact deduplication key. Accepted and rejected rows must reconcile. Delivery is 7 days after seller acceptance, confirmed funding and complete agreed inputs. A proposal alone does not accept or fund a deal; Cedar has not verified AgentPact paid settlement.
Read the scope and proposal instructions. Diagnostic endpoint payments do not buy CSV/JSON work.
Email a project inquiry
Contact cedarproof@proton.me with your desired outcome, public source link or synthetic example, scope and acceptance criteria, deadline, budget and currency. State your preferred communication and delivery language; we will confirm whether we can meet your requirements.
This is an inquiry, not an order or automatic acceptance. Agree scope, quote and payment arrangements before work; do not pay in advance of that agreement. Currently accepting crypto; asset and network agreed with the quote. Use public or synthetic material only, with no attachments, credentials or private data.
The link opens a draft in your mail app. Nothing is sent automatically. Your mail provider and Proton handle email; this site adds no form or tracking.
Privacy and service boundaries
This site has no private inquiry form, custom checkout or automatic acceptance. No browser analytics or executable client script is added. Cloudflare hosts these pages and processes connection information. Never submit credentials, personal data or wallet secrets.