canonical: https://jentic.com/apis/aiengineerprofessional.com/aiengineerprofessional # Aiengineerprofessional bicycle.guide guide registry API The Bicycle.guide API is a read-only registry of published guides, their taxonomy, and the capability spine that joins books, guides, KSAO elements, and jobs. It returns the full guide registry and a single guide's decorated row by slug, searches guides, and reports cross-book disagreements for a guide with names and provenance. The taxonomy, capability spine, and organizational conditions are all served as structured data for cooperating repos and agents. Every route is protected by a shared-secret header. ## For AI agents Search and read a registry of published guides, their taxonomy, cross-book disagreements, and the capability spine joining books, guides, KSAO elements, and jobs. ## Scope Does not author or edit content, enroll learners, or deliver courses. Use for reading and searching the published-guide registry, its taxonomy, and capability mappings only. ## Capabilities - Look up a single guide's decorated registry row by its slug - Search the guide registry for a guide - Read cross-book disagreements for a guide with names and provenance - Browse the guide program's taxonomy as structured data - Trace the capability spine that joins books, guides, KSAO elements, and jobs - Read organizational conditions including identity, label, corroboration, and causal roles ## Use cases ### Agent Lookups Against the Guide Registry An AI agent connecting through Jentic can resolve a guide and its context in a few reads: it searches the registry, reads a guide's decorated row by slug, and pulls the taxonomy to place it. Jentic injects the shared secret at call time, so the agent queries the read-only registry without ever holding the credential in its prompt. Example prompt: Search the registry for a guide, then read that guide's decorated row by its slug and return its taxonomy placement ### Taxonomy and Capability Spine Work with the guide program's vocabulary and its competency mapping as data. The Bicycle.guide API serves the taxonomy as structured values and returns the capability spine that joins books, guides, KSAO elements, and jobs, so an agent can map a job to the guides and competencies that cover it rather than parsing prose documentation. Example prompt: Read the capability spine and the taxonomy, then map a given job to the guides and KSAO elements that cover it ### Guide Search and Disagreements Find the right guide and understand where sources differ. The Bicycle.guide API searches guides or refuses with the nearest owned match, and reports cross-book disagreements for a guide with names and provenance, so an agent assembling an answer can cite the guide it drew from and flag where books disagree. Example prompt: Search guides for a topic, then read the chosen guide's cross-book disagreements to flag where sources differ ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | `/api/v1/guides` | Read the guide registry | | GET | `/api/v1/guides/{slug}` | Read a single guide's decorated row | | GET | `/api/v1/guides/search` | Search guides | | GET | `/api/v1/guides/{slug}/disagreements` | Read cross-book disagreements for a guide | | GET | `/api/v1/taxonomy` | Read the guide program's taxonomy | | GET | `/api/v1/capabilities` | Read the capability spine | | GET | `/api/v1/conditions` | Read organizational conditions | ## Key resources - **Guides** — Read the registry, a single guide by slug, search results, and cross-book disagreements - **Taxonomy** — Read the guide program's vocabulary as structured data - **Capabilities** — Read the capability spine joining books, guides, KSAO elements, and jobs - **Conditions** — Read organizational conditions including identity, label, corroboration, and causal roles ## AI readiness This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use. - **Score:** 59 / 100 - **Maturity:** Foundational - **Dimensions:** - Foundational Compliance: 80 / 100 - Developer Experience & Jentic Compatibility: 69 / 100 - AI-Readiness & Agent Experience: 51 / 100 - Agent Usability: 94 / 100 - Security: 50 / 100 - AI Discoverability: 31 / 100 - **View full report:** https://jentic.com/apis/aiengineerprofessional.com/aiengineerprofessional/scorecard - **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/ - **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview ### Score it yourself Every API in the directory is allowlisted, so you can re-score it with no key required. - **Score your own API:** https://jentic.com/scorecard.md - **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md ```sh npx @jentic/api-scorecard-cli score ``` ## Why Jentic - **Setup:** Wiring the Bicycle.guide API by hand means sending a shared secret in the x-bicycle-guide-secret header on each read and parsing the registry, taxonomy, and capability spine yourself. Through Jentic you install once, import Bicycle.guide from the API Directory, store the secret once, and your agent calls it. - **Permission scoping:** Because the whole Bicycle.guide surface is read-only, a rule can allow guide lookups, search, and taxonomy reads without exposing any destructive action. Guide slugs travel in the URL path (`/api/v1/guides/{slug}`), so a rule can also pin the agent to one guide. - **Credential handling:** Your Bicycle.guide shared secret is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'search the guide registry' or 'read the taxonomy', and Jentic returns the matching Bicycle.guide operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **Moodle** — Moodle manages courses, content, and learners in an LMS. - **Udemy** — Udemy provides a catalog of courses and their metadata. - **Airtable** — Airtable holds structured records and relations as a lightweight database. ## FAQ ### What authentication does the Bicycle.guide API use? The Bicycle.guide API authenticates with a shared secret sent in the `x-bicycle-guide-secret` header per its OpenAPI spec, and every route is protected. Through Jentic the secret is injected at call time rather than living in the agent's prompt or logs. ### 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.