Find the right service. Plug it into your agent.

The saved starter catalog contains eight entries. Four declare API key authentication, three OAuth and one none. At thirty pixels per entry the bars measure one hundred twenty, ninety and thirty. Seven entries are REST contracts and one is an MCP filesystem contract. These are saved catalog declarations, not current verification of provider documentation or service access. Search filters names, category, descriptions and capabilities as plain case insensitive substrings. Filtering narrows visible cards but does not remove services already saved to the stack. Adding Exa and Browserbase creates a two-service stack. Exa declares one environment variable and Browserbase two, so the manifest lists three requirements across those services. At eighty pixels per count Exa requirements measure eighty, Browserbase one hundred sixty and total two hundred forty. The manifest includes variable names and documentation URLs, not secret values, tokens or a working client connection. Duplicate IDs are rejected in the stack. It is a portable configuration record; export does not call a provider or prove that its credentials and permissions work. Removing one service from a two-service stack leaves one. At one hundred pixels per service the before bar is two hundred, removed one hundred and remaining one hundred. Save persists the current array in this browser, while reset clears that local storage entry. A custom contract requires a name, category, capability and a parseable documentation URL; the source checks URL parsing rather than restricting the scheme to HTTPS as its error text implies. Built-in actions still work without optional GSAP motion. Native selection, actual manifest JSON and reset must be checked independently; no real service installation or backend authorization is implied.