Developer & CI · wired today
Drive Apify with governed agents
Build, review and release state is where agents earn their keep. The Apify 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 Apify
| Tool | What it does |
|---|---|
get_me | Get the Apify account the API token belongs to (username, id and plan) |
list_actors | List the Apify Actors the token can see (id, name, owner username and modified time) |
list_actor_runs | List the runs of one Apify Actor, newest last, optionally filtered by run status |
list_datasets | List the Apify datasets the token can see (id, name and item counts) |
Every tool above is read-only. Write surfaces ship only after live testing, and always behind approval gates.
What the Apify connector needs
You provide API token from your Apify 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: Apify's own API documentation ↗ covers creating and scoping the credential.
How proven is this?
This connector was blind shape-proven against the real Apify 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.
Apify integration FAQ
What can Quox agents do with Apify?
Agents can run 4 read-only tools against Apify: get me, list actors, list actor runs, list datasets. Every call is receipted in the evidence trail.
What does the Apify integration need?
You provide API token from your Apify 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 Apify 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 Apify connector?
This connector was blind shape-proven against the real Apify 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.