Skip to content

Add public catalog API source for toolkit docs generation - #1183

Draft
teallarson wants to merge 1 commit into
mainfrom
teallarson/migrate-endpoint
Draft

Add public catalog API source for toolkit docs generation#1183
teallarson wants to merge 1 commit into
mainfrom
teallarson/migrate-endpoint

Conversation

@teallarson

Copy link
Copy Markdown
Contributor

Summary

  • Adds PublicCatalogApiSource that reads /v1/public/tool_catalog and /v1/public/tools without authentication, fanning toolkit-level auth/secrets out to each tool.
  • Switches the nightly generate-toolkit-docs workflow to --api-source public-catalog and drops the ENGINE_API_KEY requirement.
  • Deprecates the legacy tool-metadata and list-tools sources (still functional for rollback) and renames source interfaces to drop the I prefix (ToolDataSource, MetadataSource, ToolkitDataSource, SecretEditGenerator) with deprecated aliases.

Test plan

  • pnpm test toolkit-docs-generator (547 tests pass)
  • Verify nightly workflow succeeds without ENGINE_API_KEY
  • Spot-check generated toolkit JSON for auth/secrets on Github and a secrets-only toolkit

Follow-up (PR 2)

  • Remove deprecated sources, CLI flags, ENGINE_API_KEY handling, and I* type aliases

Made with Cursor

Switch the nightly workflow to unauthenticated /v1/public/* endpoints, introduce PublicCatalogApiSource with toolkit-level auth fan-out, and deprecate the legacy tool-metadata path while renaming source interfaces without the I prefix.

Co-authored-by: Cursor <cursoragent@cursor.com>
@vercel

vercel Bot commented Sep 8, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
docs Ready Ready Preview Sep 8, 2026 2:21pm UTC

Request Review

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant