Availability & response fields
Inspect HTTP status, measured response time, valid JSON and required top-level fields. Get explicit findings instead of a simple uptime badge.
An Apoplous agent / API diagnostics
DOLIHI
Observe the response.
Understand the change.
Public API checks and scheduled observations. Structured evidence for the people and agents building on them.
Finite orders · USDC on Base · No subscription
RESPONSE FIELD
01 / OBSERVE · 02 / COMPARE
01 / OBSERVE · 02 / COMPARE
ABSTRACT RESPONSE TRACE
VISUAL ONLY · NO LIVE TELEMETRY
VISUAL ONLY · NO LIVE TELEMETRY
What Dolihi checks
Go beyond “the server is up.”
Use a single diagnostic to inspect a response, or a finite monitoring order to compare observations over time.
Schema & OpenAPI checks
Supply supported JSON Schema or OpenAPI response requirements to identify mismatches in the observed response. This is response validation, not a full API certification.
JSON regression monitoring
Compare later samples with the first valid baseline. Surface changes in response shape and contract failures, with private reports and portable reproduction artifacts.
Finite orders. Clear scope.
Choose one check or a day of observations.
Single API diagnostic
One public HTTPS response, checked against the requirements you supply.
0.02 USDC / check
- HTTP status and measured response time
- JSON and required-field checks
- Supported contract validation
- Structured diagnostic result
Scheduled monitoring
24-hour API regression report
One public JSON HTTPS GET endpoint, observed after confirmed payment.
1 USDC / 24-hour order
- Up to six observations at four-hour intervals
- Fixed first valid JSON baseline
- Supplied schema and response-contract checks
- Private JSON / Markdown reports and reproduction pack
- Report access for seven days after the observation window
The live service specification and payment challenge are authoritative. Scheduled orders require available capacity; observation count and uninterrupted availability are not guaranteed. No automatic renewal. Prices are in USDC, not EUR.
Buyer workflow
Your endpoint. A defined check. A private result.
Supply the target
Send a public HTTPS endpoint and supported requirements from your application or agent.
Confirm the payment
Your x402-compatible client reads the payment challenge and authorizes USDC payment on Base.
Let the checks run
A scheduled order activates only after payment is independently confirmed. Save your returned access token privately.
Retrieve the evidence
Fetch private reports with the token in the Authorization header. Report retrieval requires no additional payment.
For applications & agents
Integrate through HTTP or MCP.
Dolihi accepts structured requests and returns machine-readable results. Use the live specification to confirm supported inputs before purchasing.
Start with the public contract
The example reads product information only. It does not create an order, sign a payment or spend funds.
Remote MCP endpoint:https://dolihi-preflight.onrender.com/mcp
Paid tool availability depends on the live service.
READ PRODUCT INFORMATION · PYTHON
import json
from urllib.request import urlopen
url = (
"https://dolihi-preflight.onrender.com"
"/products/api-regression"
)
with urlopen(url, timeout=20) as response:
product = json.load(response)
print(product["selling_enabled"])
print(product["price_usdc"])
print(product["inputSchema"])An unsigned purchase request returns HTTP 402, not a completed order. A payment-capable client is required to buy. Keep report tokens out of URLs and public pages; retrieve private reports from your backend.
Before you use it
Know the boundaries.
Do I need to own an API?
You need a public endpoint you are permitted to check. It may belong to your own service or an integration you rely on. You do not need to install Dolihi or provide an AI model key.
Does Dolihi test a complete checkout or payment flow?
No. These products inspect public responses and supported contracts. They do not execute purchases, access authenticated dashboards, prove business correctness or perform a complete security audit.
Can it monitor private or authenticated APIs?
These products accept public HTTPS targets. Upstream credentials, redirects and payments are outside their scope. Do not include secrets in the target URL or request.
What if the target fails or returns a large response?
A failed, oversized or contract-failing response produces diagnostic findings. For the 24-hour product, a baseline requires a successful JSON sample of at most 16 KiB, 2,000 nodes and depth 12. A valid baseline is not guaranteed.
Is this a subscription or an uptime guarantee?
No. The scheduled product is one prepaid, finite 24-hour order with up to six observations. It does not renew automatically, promise uninterrupted uptime or include webhook alerts.
What if a payment result is uncertain?
Do not pay again automatically. Follow the recovery flow in the live service contract using the original request ID and payment authorization. A marketplace listing or an HTTP response alone is not proof of a confirmed payment.
Build on evidence
Give your integration a second pair of eyes.
Start with a defined API check and inspect the results.