Skip to content

Add 19 developer utility APIs (hash, UUID, regex, QR, barcode, timezone, cron, JWT, JSON Schema...)#442

Open
fredericsuretat wants to merge 1 commit into
xpaysh:mainfrom
fredericsuretat:add-utility-apis
Open

Add 19 developer utility APIs (hash, UUID, regex, QR, barcode, timezone, cron, JWT, JSON Schema...)#442
fredericsuretat wants to merge 1 commit into
xpaysh:mainfrom
fredericsuretat:add-utility-apis

Conversation

@fredericsuretat
Copy link
Copy Markdown

19 general-purpose developer utility APIs for AI agents and automation pipelines. All live on Base mainnet, self-hosted, no API keys, no signup.

These complement the French data services (#415, #441) with reusable building blocks that fit any language or region:

Encoding & Crypto

Text & Data Processing

Math & Units

Visual

All discoverable via /.well-known/x402.json. FastAPI docs at /docs on each domain.

@TateLyman
Copy link
Copy Markdown

Ran a no-payment external spot-check on three of the new utility APIs. No payment headers, wallet signatures, paid calls, private endpoints, or account access.

Repro shape:

curl -i https://x402-hash.suretat.com/.well-known/x402.json
curl -i -X POST https://x402-hash.suretat.com/hash \
  -H 'content-type: application/json' \
  -H 'origin: https://suretat.com' \
  --data '{"text":"abc","algorithm":"sha256"}'

curl -i https://x402-uuid.suretat.com/.well-known/x402.json
curl -i -X POST https://x402-uuid.suretat.com/generate \
  -H 'content-type: application/json' \
  -H 'origin: https://suretat.com' \
  --data '{"version":"v4","count":1}'

Current readback:

  • The sampled discovery URLs did not return usable discovery from here. x402-hash, x402-uuid, and x402-jwt /.well-known/x402.json timed out in the batch run.
  • Some paid routes are live: Hash /hash returned a structured 402; JWT /decode returned a 402-shaped response.
  • UUID /generate returned 503 no available server from here.
  • The sampled 402s did not include Cache-Control: no-store or browser-readable CORS headers with the Origin probe.

I would treat this as a listing-readiness blocker until discovery is stable and at least one route per service is verified against the PR path. After that, the same CORS/no-store challenge headers from your earlier clean services should make these easier for browser-hosted agent clients to consume.

@fredericsuretat
Copy link
Copy Markdown
Author

Thank you for the review, @TateLyman. Issues addressed:

Discovery endpoint: All services now implement /.well-known/x402.json — confirmed 200 on hash, uuid, jwt and all 16 other services in this PR.

CORS + Cache-Control: All 402 challenge responses now include Access-Control-Allow-Origin: * and Cache-Control: no-store.

UUID 503: Was a transient load issue (temporary backend overload). UUID is now stable with GCloud failover.

All 19 services are live with stable discovery. Ready for re-review.

@TateLyman
Copy link
Copy Markdown

Re-ran a no-payment external spot-check after the updates.

Repro shape:

curl -i https://x402-hash.suretat.com/.well-known/x402.json
curl -i -X POST https://x402-hash.suretat.com/hash \
  -H 'content-type: application/json' \
  -H 'origin: https://suretat.com' \
  --data '{"text":"abc","algorithm":"sha256"}'

Current readback:

  • Sampled discovery for Hash, UUID, and JWT now returned 200 application/json.
  • Hash and JWT sampled paid routes returned structured 402 application/json before execution.
  • Those sampled 402 responses now include Access-Control-Allow-Origin: * and Cache-Control: no-store.
  • UUID is reachable; my sample body returned 422 application/json, which looks like request-schema validation rather than the earlier backend 503. Worth checking docs/examples, but the availability issue appears resolved from this path.

I did not send payment headers, sign requests, or attempt paid calls.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants