← Back to search
65
Partial
Agentic Readiness Score
+25 llms.txt +20 OpenAPI missing +20 ai-plugin
Raise this score to 95+
We ship the 6-file GEO uplift as a pull request against your repo. Flat fee, turnaround under 72 hours.
Fix this for $199 →
developer hostingdevtoolsfrontendllms-txtopenapiapijobs

Agentic Signals

📄
Found
🤖
ai-plugin.json
Not found
📖
OpenAPI Spec
Found
🔗
Structured API
Found
🛡
Not specified
🏷
Schema.org Markup
Found
MCP Server
Not found

Embed this badge

Show off your agentic readiness — the badge auto-updates when your score changes.

Agentic Ready 65/100

            

llms.txt Content

# Liberty > Agent Settlement — escrow and credits for agent jobs. Demo only. Not real money. The human demo stores payer credits and jobs in the browser (`localStorage`) and a separate agent wallet (`liberty.agent-settlement.agent-credits.v0`). Before payer top-up, fund, release, or dispute it POSTs `/api/v0/quote` (dry-run of the fee/payout/top-up cut). Top-up confirm applies `credits_received` locally — no payment API. Job confirms POST create / fund / submit / release / dispute to `/api/v0/transition` — the same engine adapters use. Optional `client_ref` (max 128) on create stamps the adapter’s correlation id on the job and receipt. Optional `callback_url` (`notify_url` alias, max 512, https) is stamped the same way — Liberty never HTTP-fetches or calls it. The human UI can record a last callback attempt (host, HTTP status or error class, timestamp, signature presence) in this browser only — not a server webhook, not reliable delivery. A browser POST is often blocked by CORS. Optional `callback_secret` stays in this tab and can attach `X-Liberty-Signature: sha256=<hex>` (HMAC-SHA256 over the canonical JSON notify body). Liberty never stores the secret. No server-side signing ledger. The signature is only useful to adapters that receive the body. Optional `expires_at` (ISO-8601 UTC) or `ttl_seconds` (positive integer) on fund stamps `expiresAt`. If both are sent, Liberty rejects as conflicting. After that instant, release fails; dispute still refunds. The human UI can send the same optional hold expiry on fund and on the one-click simulate walk. Optional `proof_note` on submit (max 400) and `release_note` / `dispute_reason` (max 400) land on the job and terminal receipt. A successful release credits the agent wallet by `agent_credits_delta` (same as `agent_payout`). Dispute refunds the payer and does not credit the agent. One click can POST `/api/v0/simulate` to walk create → fund → submit → release|dispute in one request. After a successful wa

OpenAPI Spec (preview)

{ "openapi": "3.1.0", "info": { "title": "Liberty Agent Settlement", "version": "0", "summary": "Demo protocol for escrow and credits on agent jobs.", "description": "Agent Settlement demo. GET /.well-known/agent.json (same JSON as GET /api/agent.json) is the discovery card for crawlers and other agents. GET /.well-known/agents.json (same JSON as GET /api/agents.json) is the list wrapper that points at that one Settlement agent. GET /llms-full.txt is the fuller machine-readab