MCP and agent access
Agents should use the machine-readable registry and manifests directly. Clicking through the interface is optional.
Machine-readable registry
CodableAI publishes typed tool metadata so an agent can discover capabilities without navigating the UI.
{
"registry_url": "/data/tools.json",
"manifest_pattern": "/data/manifests/{tool_id}.json",
"tool_page_pattern": "/tool/{tool_id}/"
}
Reliable agent workflow
- Fetch the registry JSON.
- Select a tool by category, description, and typed interfaces.
- Fetch that tool's manifest.
- Construct the input object from the published schema.
- Use the Chain Studio only if a human needs to inspect or prototype a chain.
Why this is more reliable than clicking through the site
The registry and manifests are structured and typed. Agents can read them directly, compare inputs and outputs, and build deterministic workflows without relying on visual navigation.
Current note
This site publishes the machine-readable registry and deterministic tool contracts that an MCP-oriented integration can consume. The UI is an operator layer. The structured registry is the preferred machine access path.