Can I search the guide registry with the Bicycle.guide API?

Yes. The search operation looks for a guide across the registry or refuses with the nearest owned match, and you can read any guide's decorated row by its slug. The taxonomy and capability spine endpoints let you place a guide within the program's vocabulary and competency mapping.

What are the rate limits for the Bicycle.guide API?

The OpenAPI spec does not specify rate limits. Check the Bicycle.guide documentation at https://bicycle.guide/docs for current limits before running a high volume of registry or search reads.

How do I look up a guide with the Bicycle.guide API through Jentic?

Search Jentic for 'search the guide registry' and it returns the search and guide-read operations with their input schema. Your agent searches the registry, then reads a guide's decorated row by its slug. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Can I limit what my agent is allowed to do with the Bicycle.guide API?

Yes. Because the whole surface is read-only, a rule can allow guide lookups, search, and taxonomy reads without exposing any destructive action, and every action it takes is logged. Guide slugs travel in the URL path, so a rule can also pin the agent to one guide.

Is there a Bicycle.guide MCP server?

You don't need an MCP server to give your agent the Bicycle.guide API. Jentic connects it directly from the API Directory: import it, store your shared secret once, and your agent calls the guide, taxonomy, and capability operations on demand without loading another server's tool definitions into its context.