Skip to content
cleo.Developers
Build reliably/Verification & limitations
Cleo documentation

Verification & limitations

Reproduce our public health and schema checks and understand what has not been tested.

Content reviewed · Maintained by Cleo Powered · Report a documentation issue · Verification basis

Observed checks

On September 30, 2026, Cleo Powered requested the deployed public health endpoints and generated OpenAPI over HTTPS, without a credential or a call submission. Both health endpoints returned HTTP 200; liveness reported ok and readiness reported ready.

The schema observed on September 30 contained both health paths and four call operations: create, get, sync, and cancel. That historical check does not verify later response fields or executor behavior. The downloadable schema includes descriptions and handler requirements that the generated schema can omit.

Reproduce without calling

Download the read-only verification script and run it with Python 3. It makes only three GET requests to public health and schema URLs, with a 30-second timeout per request. It requires no API key and does not create, sync, or cancel a call.

Terminal
python verify_public_api.py

The output contains current HTTP statuses, health responses, and schema paths. Keep your execution date with the output. A later run can differ if availability or the contract changes.

What this does not prove

Health and schema checks do not establish that your account may dial, that a particular destination works, or that a phone errand succeeds. This record is first-hand infrastructure evidence, not a customer outcome study.

Call completion does not prove a booking or answer was obtained. Structured extraction uses available recipient evidence; summaries and results can be null or incomplete. See results and schemas. The public call object exposes summary, extraction metadata, and fallback transcript fields.

The eight bot guides are reviewed setup recipes. Third-party editor imports and bot execution have not been verified, and no native platform partnership is claimed. No live call was placed during these documentation checks.

Documentation history

  • September 19, 2026: core reference reflects provider metadata, nullable summaries, and result-schema limitations.
  • September 30, 2026: eight bot guides, dark theme, public access prerequisites, shared publisher/page metadata, and this reproducible verification record.

Page review dates identify content reviews, not automatic runtime certification. Send corrections to hello@cleopowered.com. For an approved live trial, use the self-call quickstart after reviewing its consequences.

NextBot integrations
Documentation
Get an API key

Explore the docs

IntroductionSubmit a phone errand, follow the call, and inspect its outcome.Bot account onboardingRegister from Muse or another bot, verify your phone, receive an API key, and set your dashboard password by email.API overviewWhich endpoints are available, how they authenticate, and what is supported today.Make your first callCall your own phone, refresh its status, and inspect the returned call data.AuthenticationCreate a key in Cleo and authenticate requests with a bearer token.Create a callQueue one bounded phone task and receive durable task and call IDs.Get a callRead the most recently saved state of a call.Sync a callRefresh a call from the calling service and retrieve its latest saved state.Cancel a callCancel queued work or request a stop, then follow confirmation.The call objectThe shared response returned by create, get, sync, and cancel.Health checksCheck API liveness and readiness without an API key or placing a call.Results & schemasUnderstand result_schema, returned metadata, and what result_schema_valid does and does not establish.Task and call lifecycleFollow a call from acceptance to its final outcome.Idempotency & retriesRecover from an interrupted request without accidentally placing a second call.Safety & permissionsHow Cleo evaluates a call task before it can dial.Errors & troubleshootingUnderstand API errors and choose a safe next step.LimitsKeep call tasks bounded and leave room for API rate limits.Verification & limitationsReproduce our public health and schema checks and understand what has not been tested.Bot integrationsChoose a route for connecting your assistant to Cleo's public API.ChatGPTConfigure a private GPT Action with Cleo OpenAPI and bearer authentication.ClaudeConnect Claude client tools or a Claude Code shell workflow.Grok & Grok BotConnect xAI function tools and check Grok Bot execution requirements.OpenClawInstall a local skill for an approved Cleo calling workflow.GeminiMap Gemini function declarations to Cleo REST operations.Copilot StudioAdd Cleo through a REST API tool, custom connector, or flow.n8nBuild an authenticated HTTP workflow with durable call recovery.ZapierBuild a private Zapier integration for approved Cleo calls.