<!-- Generated by scripts/build_openapi_skill_references.py; do not edit. -->
# OpenAPI contract: Integration Architect routing summary

## Provenance

- Source: `ycloud-api-v2.yaml` (pinned release snapshot).
- Source SHA-256: `8592bd4cc37186655a480dd86ce6bac6731543727327a2871d9103a0b8ed9e81`
- OpenAPI version: `3.0.0`
- API info.version: `v2`
- This derived reference does not replace the upstream API Owner's canonical source.
- Generated deterministically from normalized JSON; do not edit this file by hand.

## Scope and handoff

- Route broad integration planning across the sixteen covered API/auth domains. Load only the selected domain reference after routing; this file intentionally contains no API operation.
- Operation coverage: `0`

## Routing matrix

| User intent | Domain Skill | Handoff |
| --- | --- | --- |
| server-side API key, environment isolation, rotation boundary | Authentication | provide auth prerequisites before API calls |
| direct/queued message send or message retrieve | WhatsApp Messages | use media/template references only when needed |
| multipart media upload | WhatsApp Media | pass returned media ID to Messages |
| template lifecycle or analytics | WhatsApp Templates | hand off sending an existing template to Messages |
| webhook endpoint lifecycle or receiver security | Webhook Endpoints | endpoint CRUD uses OpenAPI; receiver behavior uses reviewed runtime facts |
| WABA discovery or optimization settings | WhatsApp Business Accounts | pass opaque WABA identity to Phone Numbers/Messages/Templates |
| phone registration, profile, commerce, username, or settings | WhatsApp Phone Numbers | consume WABA identity and expose confirmed sender configuration |
| group lifecycle, membership, invite links, or settings | WhatsApp Groups | pass confirmed group identity to Messages |
| Flow lifecycle, preview, publish, deprecate, or delete | WhatsApp Flows | pass confirmed Flow identity/status to Messages |
| mark inbound message read or show typing | WhatsApp Inbound Messages | consume Receiver message identity |
| account balance readiness | Balance | provide a read-only readiness signal |

## Required planning output

`Prerequisites`, `Architecture`, `Implementation Plan`, `Tests`, `CANNOT`, and `Next Steps`.

## Codegen interpretation

- Routing is based on user intent and source tags, not on guessed SDK method names.
- This OpenAPI snapshot does not define cross-cutting runtime behavior. Consult the reviewed `runtime.md`; if neither source confirms a fact, do not fill it in.