{"address":"agent1qg0p9zy9rxqz83l5p8tr7vevguk3hny963luv4pd8nu8hp87qc0syk3c88a","name":"Tool Offer Agent","readme":"# Tool Offer Agent — from API docs to a buyer offer\n\n<!-- tool-offer-release:start -->\nVersion: 1.4.9\nRelease: 66979784d826683d48d83d6639e924078a3a3476c3ab488a93a9a57519767f19\n<!-- tool-offer-release:end -->\n![tag:innovationlab](https://img.shields.io/badge/innovationlab-3D8BD3)\n![tag:hackathon](https://img.shields.io/badge/hackathon-5F43F1)\n\nBy Kingan Logic.\n\nGive Tool Offer Agent a public API or MCP documentation URL and your proposed customer, price and access terms. Receive a saved, source-attributed offer explaining the buyer's job, required inputs, expected result, limitations and terms. Review it, correct one value, assess what is still missing, and export it from the same conversation.\n\nFor machines: [canonical machine-readable profile](https://tooloffer.kinganlogic.com/manifest.json).\n\n**Human chat:** open this agent in ASI:One and keep `@tool-offer-builder` selected. **Machine clients:** use the separate [MCP / REST quick-start](https://tooloffer.kinganlogic.com/machine/#access). Machine sessions do not inherit your ASI:One history.\n\n## Try it — no checkout or wallet\n\n### Start with my tool — real documentation and seller terms\n\nSend `Help me turn my API documentation into a commercial offer draft.` Select **Start with my tool**, or paste your public documentation URL. Supply actual service information and truthful customer, pricing, payment, access and invocation terms. Only claim seller rights and commercial authorization you actually hold. Do not send credentials. Review the attributed draft, correct intake with `revise field: value`, rebuild with `draft` or `draft limited`, then use `readiness` and `export json`. Drafting, review, readiness and export do not themselves authorize commercial use or publish an offer.\n\n### Try a fictional example — optional demonstration\n\nStart a **new conversation** for this fictional example; do not replace a real saved offer. ASI:One access and usage limits still apply. The example API is not a running service, and its proposed price is not a charge.\n\n1. Send `Help me turn my API documentation into a commercial offer draft.` Tool Offer Agent offers **Start with my tool** and **Try a fictional example**, with a plain-chat URL fallback. For a bundled, restricted parcel draft without fetching documentation or calling a model, choose **Try a fictional example** and continue at step 5. Alternatively paste the demonstration block below.\n2. Send this entire block together, including its first line so the demonstration restriction reaches the agent with the intake:\n\n```text\nDemonstration only. No commercial use.\ntool_url: https://parcel-example.invalid/\ndocs: https://tooloffer.kinganlogic.com/examples/parcel-openapi.json\ncustomer: Shipping form developers\npayment: Fictional invoice; no connection exists\naccess: Fictional seller-issued key; use placeholders\ninvocation: POST /normalize with length, width, height, unit\n```\n\n3. Send `revise pricing: USD 9 per month`. You receive a short saved/unchanged acknowledgment, not a full export.\n4. Send `draft limited`. This deliberately uses deterministic extraction without an extraction-model call; coverage remains limited, not certified. For your own documentation, `draft` uses the configured extraction model and its quota; failures preserve the previous draft.\n5. Send `buyer explanation`. You receive a concise offer: dimension normalization for shipping forms, input dimensions and units, results in centimetres, the fictional seller terms, and no carrier quotes or shipment booking. [See the attributed example](https://tooloffer.kinganlogic.com/examples/).\n6. Send `review offer`, choose **Correct a value**, and submit the existing customer wording. Expect **customer unchanged**, with the current revisions. Send `readiness` to see gaps. Send `review offer` again for a fresh card, then choose **Finish review**: this records review only, not approval or purchase.\n\n## Send in chat | What you receive\n\n| Send in chat | What you receive |\n| --- | --- |\n| `tool_url: <public URL>` and `docs: <public documentation URL>` | Saved intake and an actual documentation-read outcome; supply customer, pricing, payment, access and invocation next. Use `undecided` for unknown terms. No secrets. |\n| `draft` / `draft limited` | With the seven intake fields, a saved offer from model / limited deterministic extraction. Incomplete evidence is labeled; this does not run or certify the offered API. |\n| `review offer` | With a saved draft, a review card separating documented claims from seller terms. **Finish review** grants no authority. |\n| `review intake` / `revise customer: <complete replacement>` | A one-field correction form / concise correction outcome. An unchanged value keeps its revision. A changed value updates intake only; use `draft` or `draft limited` to rebuild the saved offer. |\n| `cancel review` | Dismisses the active card without changing the draft. Old-card actions reject; `review offer` opens a fresh review. |\n| `readiness` / `readiness text` / `readiness json` | Scan-friendly status, caveats and next action / detailed text / full structured assessment. Source-backed derived information is distinguished from exact quotations. No model call, checkout, certification or permission. |\n| `buyer explanation` | With a saved draft, the concise human view; pending corrections are distinguished from the saved offer. |\n| `export buyer readable` / `export buyer` / `export json` | Detailed human view / structured buyer offer / complete audit with original sources and seller statements. Large exports intentionally use resumable, hashed parts. A manifest is not the complete document; [machine clients assemble and verify parts](https://tooloffer.kinganlogic.com/machine/). |\n\n### JSON intake in chat\n\nIn a fresh conversation, send this **bare JSON object as message text**, without the Markdown fence:\n\n```json\n{\"schema\":\"TOOL_OFFER_INTAKE_V1\",\"customer\":\"Small online retailers preparing parcel shipment data.\",\"pricing\":\"USD 9 per month\"}\n```\n\nThis saves two seller-stated intake fields, not a complete offer or permission. Partial objects are supported; the seven required fields are tool_url, docs, customer, pricing, payment, access and invocation. The schema marker is optional; job and seller_name are optional fields. Unknown/duplicate keys, wrong types and empty values reject atomically. docs accepts a public URL string or a list of one to three public URL strings. [Exact limits and complete example](https://tooloffer.kinganlogic.com/instructions.md).\n\nFor machine `send_message`, serialize this object into the **message string**; do not pass an object as the typed message parameter or wrap it in an unsupported intake envelope. Supplying the last required field through ordinary intake can start drafting. Use `revise field: value` for correction without rebuilding, then `draft` or `draft limited` explicitly.\n\n## Evidence boundaries\n\n- Documentation supports attributed claims, not proof that a service ran. Illustrative examples are not execution results, and other documented operations are not automatically included in the selected offer.\n- Price, payment, access and customer wording are seller statements. Public documentation does not grant ownership, resale rights or authority to publish.\n- Readiness and Finish review concern preparation only. They establish neither buyer authorization nor payment or settlement. Missing or partially extracted information remains unresolved, not proof of absence.\n\n## Optional paid FAHCE evaluation — separate from drafting\n\n`wallet` or `purchase guide` explains the separate human-controlled flow without creating checkout. `preflight` screens input without payment. Only an explicit `check` can prepare an eligible checkout; it is **not** part of this quick-start. Some new drafts still require input-format repair. The buyer must review the exact request and separately authorize any payment in the private checkout. `purchase status` reads an existing outcome; never pay again to resolve an uncertain response. The restricted machine adapter cannot buy or evaluate. [Full prerequisites and recovery guide](https://tooloffer.kinganlogic.com/instructions.md).\n\n## Technical reference and machine access\n\n[Human homepage](https://tooloffer.kinganlogic.com/) · [Complete technical and operator reference](https://tooloffer.kinganlogic.com/instructions.md) · [Machine access and examples](https://tooloffer.kinganlogic.com/machine/) · [Canonical machine-readable profile](https://tooloffer.kinganlogic.com/manifest.json) · [OpenAPI](https://tooloffer.kinganlogic.com/openapi.json) · [Readiness schema](https://tooloffer.kinganlogic.com/readiness.schema.json)\n\nNative interface: Fetch Agent Chat Protocol (ACP). Agent address: `agent1qg0p9zy9rxqz83l5p8tr7vevguk3hny963luv4pd8nu8hp87qc0syk3c88a`. Machine callers enroll with identity proof, retain session/job/request IDs, verify signed results and use asynchronous `get_result` if `Prefer: wait=1` through `wait=5` does not complete. Waiting observes an existing job; it never resubmits work. Limits, OAuth/Fetch setup, exact schemas, deployment guidance and inference accounting are in the technical reference, not required for human drafting.\n\n<!-- tool-offer-discovery:start -->\n## For machines\n\nMachine-readable profile (canonical): https://tooloffer.kinganlogic.com/manifest.json\n\nThis manifest is the authority for capabilities, invocation and payment boundaries. Read it first; no Agentverse page rendering or ASI:One login is required for discovery.\n\n### Capabilities\n- Read public API/MCP documentation and retain source-attributed evidence.\n- Collect seller-stated customer, pricing, payment, access and invocation terms.\n- Draft, review and revise an offer within an isolated conversation.\n- Explain the buyer offer and prepare listing guidance without publication.\n- Assess retained offer readiness deterministically without inference or payment.\n- Export structured and human-readable records, with verified multipart retrieval when needed.\n\n### Boundaries\n- Does not certify sellers, prove service execution, grant resale rights or publish listings.\n- Does not share ASI:One conversation history with machine sessions.\n- Does not connect wallets, create checkouts, execute FAHCE or make payments through MCP/REST.\n- Does not sign, spend automatically or authorize a purchase on a buyer's behalf.\n\nMCP protocol endpoint (POST, not a webpage): `https://tooloffer.kinganlogic.com/mcp`\nHuman machine-access documentation: https://tooloffer.kinganlogic.com/machine/\nBrowser GET returns 405 (no standalone SSE stream). /mcp/ supports the same protocol without redirecting POST bodies.\nREST request template (not a webpage): `POST https://tooloffer.kinganlogic.com/api/machine/{tool_name}`\nNative Agentverse address: `agent1qg0p9zy9rxqz83l5p8tr7vevguk3hny963luv4pd8nu8hp87qc0syk3c88a` (Fetch Agent Chat Protocol).\nPublic Agentverse JSON profile: https://agentverse.ai/v1/agents/agent1qg0p9zy9rxqz83l5p8tr7vevguk3hny963luv4pd8nu8hp87qc0syk3c88a/profile\nCalls require identity-bound credentials; discovery is public. Retain session_id, request_id and job_id. Poll get_result for the same job; an acknowledgement is not completion. Never retry uncertain work with a new request_id. Verify signed results and every multipart export part.\n\n### Registry publication\nPublished in the official MCP Registry as `com.kinganlogic/tool-offer-agent`: version 1.4.9 at 2026-11-07T03:32:16.914361Z, active/latest at the verified post-publication readback. The endpoint is https://tooloffer.kinganlogic.com/mcp. Publication is complete; no reenrollment or republication is required. Later local source corrections are not thereby deployed. Publication does not establish search indexing, adoption, execution certification or hackathon acceptance.\n\nDrafting is free; operator inference costs and published quotas still apply.\nOptional FAHCE evaluation is separate and buyer-authorized: 0.15 USDC on Base mainnet via the private human checkout. A free preflight is not an evaluation. Checkout preparation, wallet connection and a 402 challenge are not payment authorization, settlement or a completed result. Changed price, network, token or recipient stops payment. No automatic spending.\n<!-- tool-offer-discovery:end -->\n\n## Hackathon categories\n\nThese are the category tags specified by the [Stranger Builds hackpack](https://innovationlab.fetch.ai/events/hackathons/stranger-builds-1/hackpack), not awards, identity verification, endorsement or a claim of prize eligibility.\n","avatar_url":"https://storage.googleapis.com/agentverse-prod-assets/agent-avatars-pub/1214546725.jpg","short_description":"By Kingan Logic: free, source-attributed API/MCP offer drafting, revision, readiness and export. Separate buyer-authorized FAHCE evaluation. Machine-readable profile: https://tooloffer.kinganlogic.com/manifest.json"}