verapli
Sign inJoin free
Menu

Guides · messaging · Everyday developer services

Quo (formerly OpenPhone) API

Business phone system (calls, texts, contacts) with an API included in Quo plans. Texting US numbers via the API needs US Carrier Registration.

Researched · not yet run liveLast researched 25 October 2026 · Quo · provider site

Researched, not yet run live. Built from the provider’s official pages (linked below). A person hasn’t walked this flow end to end yet, so check each step against the source.
Do this with verapliJSON for agents

Steps

Steps marked “human step” are ones only you can do: verapli never signs in, submits, pays or accepts terms for you.

  1. Sign in or create a Quo account

    Sign in to Quo. If you have no account yet, you create it yourself; verapli does not create accounts.

    • Guided by hand
    • Human step: You sign in

    Where: https://my.quo.com/

  2. Start a trial or plan

    Quo has a 7-day free trial; API access is included in Quo plans.

    • Guided by hand
    • Human step: You add payment details
    • After: Sign in or create a Quo account

  3. Generate an API key

    As a workspace owner or admin, open workspace settings > API, click Generate API key and give it a label without spaces. Send it as the raw Authorization header (not Bearer).

    • Guided by hand
    • Human step: You press submit
    • After: Start a trial or plan

    verapli captures QUO_API_KEY here by plain code: encrypted in your browser, never shown to AI.

  4. Complete US Carrier Registration (to text US numbers)

    Before sending texts to US numbers via the API, complete US Carrier Registration in Quo.

    • Guided by hand
    • Human step: The provider reviews it
    • After: Start a trial or plan

Terms and gotchas

Plain-English summary, not legal advice. Each card links its source.

Can cost moneyThe rules say

US carrier registration

Texting US numbers through the API requires completed US Carrier Registration. [5]

What you end up with

Env varSecretFormatWhat it is
QUO_API_KEYsecretQuo API key. Quo's docs name no env var; this name is a verapli convention.

Pricing

  • Free tier: 7-day free trial.
  • Costs: Starter from $180/year, Business $276/year, Scale $420/year.

Source [3]

For agents

The same entry as JSON: /api/v1/entries/quo/app · requirements /api/v1/requirements/quo/app · terms /api/v1/terms/quo/app.

Remote MCP (read-only, no auth)
claude mcp add --transport http verapli https://verapli.com/mcp

> "What do I need for Quo (formerly OpenPhone) API, and how long will it take?"
  → tools/call requirements { "provider_id": "quo/app" }

Sources

  1. Stripe Projects CLI (Available providers) Quo is listed as a Stripe Projects provider (Communications) · accessed 25 October 2026 · official
  2. projects.dev provider catalogue Catalogue service id quo/app · accessed 25 October 2026 · official
  3. Quo Quo is formerly OpenPhone; Starter from $180/year, Business $276/year, Scale $420/year; 7-day free trial · accessed 25 October 2026 · official
  4. Quo API API access included in Quo plans; API key authentication; SMS but not MMS · accessed 25 October 2026 · official
  5. Quo API docs - Authentication Workspace settings > API tab, owners or admins only; Generate API key with a label without spaces; Authorization header with the raw key, not Bearer; US Carrier Registration required to text US numbers via API · accessed 25 October 2026 · official
  6. Quo API docs - Send your first message E.164 numbers; userId and from from GET Phone Numbers; US Carrier Registration for texting US numbers · accessed 25 October 2026 · official

Provider rules change. This page is generated from verapli registry version 2026.1025.316; spotted something out of date? Tell us. Quo is not affiliated with verapli.