Marketing & email · wired today

What can agents actually do with Bitly?

Campaign and audience data drives half the questions agents get asked. The Bitly connector is one of 205 executable connectors and gives agents 3 read-only tools, with the credential held in the vault and every call receipted.

The Bitly tool list, exactly as agents see it

get_user — Get the authenticated Bitly user (login, name, default group and email verification state)
list_groups — List Bitly groups the authenticated user can access (group_guid values for the other tools)
list_bitlinks — List the Bitlinks in one Bitly group, newest first

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

What the Bitly connector needs

You provide access token from your Bitly account; Quox sends it as a bearer token. 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: Bitly's own API documentation ↗ covers creating and scoping the credential.

How proven is this?

This connector was blind shape-proven against the real Bitly 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.

Bitly integration FAQ

What can Quox agents do with Bitly?

Agents can run 3 read-only tools against Bitly: get user, list groups, list bitlinks. Every call is receipted in the evidence trail.

What does the Bitly integration need?

You provide access token from your Bitly account; Quox sends it as a bearer token. 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 Bitly 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 Bitly connector?