Tool reference
Give an agent the same KEEL workflow as Studio.
Discovery, contract inspection, asset planning, safe reuse, prepared publication, and explicit wallet review.
Connect and discover
The public machine-readable endpoints describe the current installation. Load tool schemas from the configured MCP server.
Installation discovery
Use /.well-known/keel.json for public connection details, /llms.txt for agent guidance, and /api/access/schema for declared access capabilities. Authenticated access and provider configuration remain server-controlled; these public documents do not grant permissions.
GET https://onkeel.io/.well-known/keel.json
GET https://onkeel.io/llms.txt
GET https://studio.onkeel.io/api/access/schemaContract-first discovery
Read the target repository and relevant docs, run keel-contract-workflow-preflight, then inspect engine modules, selected network, compatible library modules, and exact contract controls. A supplied ABI proves neither code identity nor user authority.
keel-contract-workflow-preflight
keel-engine-catalog
keel-network-inspect
keel-library-search
keel-contract-controlsPrepare and validate
Pass arguments from each advertised tool schema. This list describes roles, not a substitute for those schemas.
Reuse and revision
keel-inline-reuse-plan inspects existing objects and returns review-only reuse evidence. For changed source, a revision plan distinguishes unchanged references from new resources. Do not republish an unchanged graph just because the agent started a fresh conversation.
Preparation
keel-inline-prepare handles supported new creator source, preserving both viewer and payloadStorage. Omitted choices use the verification shell and Compact storage. Existing compatible prepared objects take the reuse route first.
Full return checking
keel-inline-token-audit inspects actual delivery bytes. keel-inline-publication-check checks expected-versus-returned prepared COPY evidence before publish-plan. The publication plan binds the concrete check and still needs receipt authentication, selected-chain read-back, and browser verification.