Y2 Developer Resources

Build agents and applications on the documented Y2 contract

Y2 exposes source-backed intelligence workflows through a versioned HTTP API, webhooks, and a separately distributed MCP package. Start from the OpenAPI 3.1 contract when generating functions or clients, then use the authentication and scope guide to create the narrowest API key for the job. API responses include version, request, and rate-limit headers; failures use machine-readable Problem Details JSON with a stable code and a recovery hint.

Choose access for your first integration

New API keys require Pro or Elite, including keys used by the MCP server. A Lite trial does not include new API-key creation. Webhook delivery itself starts with Lite; a connector that retrieves the full report also needs API access. Review pricing and the exact workspace limits before setup.

For a complete example, follow the OSINT MCP walkthrough or build a recurring intelligence briefing.

Machine-readable contracts

• Y2 OpenAPI 3.1 JSON for agents, function calling, and client generators
• Y2 OpenAPI 3.1 YAML as the canonical, human-reviewable contract
• Y2 llms.txt for when-to-use guidance and the curated documentation index
• Y2 sitemap for all crawlable public pages

Authentication, errors, and delivery

Use Y2 API authentication for bearer-key format, workspace binding, scopes, rate limits, and error handling. The API overview identifies the v1 and v2 base paths and current availability. For event-driven integrations, read the webhook API and delivery and signature guide before accepting production events.

MCP and agent workflows

The Y2 MCP guide documents the separately distributed local stdio server, client configuration, least-privilege scopes, and inspection workflow. Use the installed server's tools/list, resources/list, and prompts/list responses as the authoritative manifest. For direct model-facing HTTP work, select operations by their unique operationId in OpenAPI and validate arguments against the published parameter and request schemas.

Choosing the right integration

Use the REST API for explicit reads and writes, webhooks for configured asynchronous delivery, and MCP when a supported local agent client should discover and call Y2 tools. Keep API keys server-side, grant only required scopes, persist request IDs for diagnostics, and review consequential intelligence against its cited sources. Contact [email protected] with the method, path, status, error code, and request ID when a documented request does not behave as expected.