context-hub-bridge

To retrieve external API documentation, agents use the chub CLI to search and fetch up-to-date specs for third-party APIs. This routing layer directs agents to query chub for the latest docs before writing any integration code.

Managing token budgets involves using the incremental fetching guidance provided by the context-hub-bridge. It directs agents to fetch API documentation in chunks, preventing context window overflow while maintaining access to necessary external API specs.

Agent routing prioritizes external API documentation via Context Hub, then falls back to internal project knowledge, and finally checks established coding patterns. This ensures the agent uses the most relevant knowledge source available for the query.

Yes, you can annotate API usage notes and gotchas for future sessions. The learning persistence feature enables agents to recall specific version requirements or integration notes discovered during previous external API documentation fetches.

To integrate with Stripe without outdated docs, the agent first uses chub search stripe and chub get stripe/api to retrieve the latest documentation. This ensures accurate, current external API documentation before writing any code.