Can I search the guide registry with the Bicycle Guide Registry API?

Yes. You can list the full registry, fetch a guide by slug, and run a search that returns matching guides or the nearest owned guide when none matches. The taxonomy and capability spine let you map a guide to its vocabulary and to jobs.

What are the rate limits for the Bicycle Guide Registry API?

The OpenAPI spec does not define rate limits for the Bicycle Guide Registry API. Check the Bicycle Guide documentation at https://bicycle.guide/docs for current limits.

Is there a Bicycle Guide Registry MCP server?

Yes, the same registry data is also served over its own MCP endpoint. You can also connect it directly through Jentic: your agent gets the full 8-endpoint surface without loading another server's tool definitions into its context, your secret is injected at call time by your self-hosted instance instead of living in a config file, and your rules decide which operations the agent may call.

Can I limit what my agent is allowed to do with the Bicycle Guide Registry API?

Yes. Every operation is a read, so a rule can allow just the registry and taxonomy reads your agent needs and nothing can modify data. Because the operations are read-only, the worst an over-broad rule allows is reading more of the registry. Every call the agent makes is logged.

How do I read the guide registry with the Bicycle Guide Registry API through Jentic?

Search Jentic for 'search the guide registry', and it returns the matching operations with their input schemas. Your agent searches guides, fetches a guide by slug, and reads the taxonomy in one run. To run it on your own infrastructure, install Jentic One from its GitHub repo.