Get started

Commerce & finance · wired today

Drive Recurly with governed agents

Money data demands the strictest governance of anything agents touch. The Recurly connector is one of 205 executable connectors and gives agents 4 read-only tools, with the credential held in the vault and every call receipted.

What agents can run against Recurly

ToolWhat it does
list_sitesList the Recurly sites the API key can see (subdomain, live or sandbox mode)
list_accountsList Recurly accounts (customers), optionally filtered by exact email address
list_subscriptionsList Recurly subscriptions, optionally filtered by state
list_invoicesList Recurly invoices, optionally filtered by state and invoice type

Every tool above is read-only. Write surfaces ship only after live testing, and always behind approval gates.

What the Recurly connector needs

You provide API key from your Recurly account; Quox sends it as HTTP basic credentials. The credential is stored encrypted in the vault and resolved just-in-time, so agents use it without ever seeing it.

Where to get it: Recurly's own API documentation ↗ covers creating and scoping the credential.

How proven is this?

This connector was blind shape-proven against the real Recurly API: every endpoint it declares answered measurably differently from a deliberately bogus control request, without any account or credential involved. It is Beta: proven against the live API surface, not yet run with a real credential.

Recurly integration FAQ

What can Quox agents do with Recurly?

Agents can run 4 read-only tools against Recurly: list sites, list accounts, list subscriptions, list invoices. Every call is receipted in the evidence trail.

What does the Recurly integration need?

You provide API key from your Recurly account; Quox sends it as HTTP basic credentials. The credential is stored encrypted in the vault and resolved just-in-time, so agents use it without ever seeing it.

Do agents see my Recurly credentials?

No. Credentials live encrypted in the Quox vault and are resolved server-side at call time. Agents invoke tools; they never receive the underlying secret.

How proven is the Recurly connector?

This connector was blind shape-proven against the real Recurly API: every endpoint it declares answered measurably differently from a deliberately bogus control request, without any account or credential involved. It is Beta: proven against the live API surface, not yet run with a real credential.