FabricBloc agent integrations should expose narrow wallet, token, NFT, and docs actions through host-specific tools rather than broad account access.
MCP servers
Model Context Protocol servers should describe each FabricBloc action in terms of capability, required scope, input contract, and expected side effect. Tool descriptions should point agents to public docs and generated API reference pages.
Claude and Codex
Claude and Codex integrations should use the same public service facts as human developers. Route docs, llms.txt, and generated API references are built so tool-using agents can fetch stable service pages, OpenAPI artifacts, and reviewed examples before acting.
Credential boundaries
Agent credentials should be short-lived where possible, scoped to a project, and restricted to the minimum capability. Do not embed secrets in docs pages, generated examples, or client-side JavaScript.
Review loop
Agent-facing examples must be deterministic and reviewable. If an example is generated upstream, the public site renders it only after the docs catalog says it has been reviewed.