Capability availability
Tell planned capabilities, missing prerequisites and accepted production behavior apart.
On this page
Availability describes a specific workflow for a specific audience. It is not a property of an entire repository, provider or marketing page.
Labels used in these docs
| Label | Meaning |
|---|---|
| Release contract | The scoped implementation target; deployment and acceptance are separately verified. |
| Planned API | An intended business outcome that cannot be called in this release. |
| Configuration required | Necessary setup is incomplete; work is not ready to execute. |
| Instructions published | A reviewed guide exists; it does not prove a connection. |
| Connection not available | No supported operational connection is enabled by this release. |
| Restricted partner topic | Separate partner/operator authority is required. |
This release
The developer entry and key contract are authentication-only. The free check does not require a workspace or billing. Business APIs are planned, and all integration-directory entries state that their connections are unavailable.
Local implementation, tests, deployment, configured providers and natural customer acceptance remain different evidence. This documentation does not claim a fresh production check.
Read results truthfully
An empty result means the supported query found nothing only when the underlying evidence is complete enough to say so. Unavailable, stale, partial, seeded and provider-uncertain results must not masquerade as zeros or success.
When a guide is not actionable
Use its inputs, outputs and boundary to plan your application. Do not guess endpoints, reuse private tool names or add funds hoping that an unavailable capability will become enabled.