# Integrations as curated API docs, not prebuilt connectors

> General Input integrations pair a secure connection with a curated API reference the agent codes against. Over 90 services were documented by February.

Feb 19, 2026. Topics: Integrations, Agents. https://www.generalinput.com/changelog/2026-02-19-integrations-documented-for-the-agent

Most automation tools can only do what their prebuilt connectors expose. In General Input, an integration is two things: a way to connect your account (OAuth or an API key) and a curated API reference the agent reads before writing code against that service. That means the agent can use almost anything the service's API supports. By February 19, more than 90 services were documented and close to 60 could be connected, including Google Workspace, Microsoft 365, [Slack](/apps/slack), [GitHub](/apps/github), [Notion](/apps/notion), [Stripe](/apps/stripe), and [Zendesk](/apps/zendesk).

### How it works

- **One record per service.** Each catalog entry holds the connection settings, a key setup guide, and the API reference, so the connection screens and the agent's docs never disagree.
- **Hybrid search.** The agent finds the right docs by meaning and by keyword, blending embedding similarity with full-text search.
- **No guessing.** The agent must read a service's docs before calling it, and if a service isn't documented it says so and suggests a documented alternative instead of inventing endpoints.
- **Docs that keep up.** Documentation agents research new services and audit existing docs against the live API.