Public URL Check API: HTTP Status + SHA-256

One public URL in; one JSON observation out. $0.001 USDC per call via x402 v2 exact on Base mainnet. No account or API key. Runtime payment challenges are authoritative.

For URL verification before citing or comparing a web resource: an independent HTTP status check, final URL, content type/encoding, raw response-body byte count, SHA-256 fingerprint and UTC observation time.

Buyer quickstart | Inspection-first Node example | JSON catalog | OpenAPI

Evaluate, pay, receive

  1. Read free metadata and receipt schema. Reproduce the free hash fixture below.
  2. GET the primary endpoint with one URL-encoded url parameter; inspect its unpaid HTTP 402 challenge.
  3. Within your own approved budget, use an x402 client to sign its payment terms and submit the same target once.
  4. Require service HTTP 200, a valid matching receipt, and a successful PAYMENT-RESPONSE. Keep the result and payment evidence.
GET https://playbrightgaming.com/agent-services-mainnet/verify-url?url=https%3A%2F%2Fplaybrightgaming.com%2Fagents%2Fpennybot-test-vector.txt

The running API executes automatically during this request. Its normal path does not wait for a person or a ChatGPT task. This is a synchronous observation, not a continuing monitor.

Exact output and useful limits

pennybot.url-receipt.v2 returns requestedUrl, finalUrl, status, contentType, contentEncoding, byteLength, sha256, fetchedAt, plus its receipt version and byte contract. It does not return the page body.

A complete target HTTP 404 or 500 is a valid, billable observation; the target status is inside the JSON. Maximum body: 1,000,000 bytes. Maximum redirects: 3. One 7-second fetch deadline. Public HTTP(S), ports 80/443; one URL of at most 2,048 characters. Signed execution and recovery retain a shared limit of 8 concurrent requests, burst 20 and refill 1/second. Free health, metadata and unsigned challenges use separate bounded pools; metadata and challenges also have per-route limits. A directory sweep cannot consume signed execution tokens. All pools can still return 429 with Retry-After under load; unsigned access is not unlimited. See the catalog admission policy or GET /agent-services-mainnet/health for exact limits.

No browser rendering, authentication/cookies, private destinations, semantic-truth determination, malware verdict, or signed/legal attestation. Website-change detection requires your own repeated observations and comparison.

Reproducible free hash fixture

URL: https://playbrightgaming.com/agents/pennybot-test-vector.txt
Exact body: PENNYBOT-URL-EVIDENCE-TEST-V1
Encoding: ASCII/UTF-8; no BOM, CR, LF, or trailing spaces
Bytes: 29
SHA-256: d053565c5bbce20a8970214dd6b46b226e11efd911366267afd8e80b759cf987

This free resource validates byte/hash reproduction; it is not a free execution of the paid endpoint. The hash covers content-encoded response-body bytes without application decompression. Headers and transfer framing are excluded.

Security and delivery boundaries

PennyBot validates public DNS answers, pins the selected destination, validates the connected peer, and revalidates redirects. Private/special-use destinations and HTTPS-to-HTTP downgrade redirects are rejected.

The live API durably stores the original order and result. Retain your original request, signed authorization and private Idempotency-Key. Exact replay returns the original bytes without refetching or settling again. Read the delivery and recovery contract; uncertain payment, missing retained output or unavailable storage can still require incident handling. No automatic-refund guarantee is made.

Full service contract, errors and acceptance | General Bright Gaming contact form | llms.txt