Execute API
Pick the best capability for a plain-language instruction and run it with the real deterministic engine. The model only routes; it never executes. Limited preview: availability is controlled by a feature flag.
What it does
Route a plain-language instruction to the right capability and run it.
When to use it
Reach for Execute when you need to answer: “Just tell me what to do with this data.” It sits in the Orchestrate stage of the catalog — run several operations at once.
Endpoint & cost
POST /api/v1/execute
Cost: Variable. Zaps draw down your shared monthly allowance; requests that fail validation are not charged.
Authentication
Send your key as a bearer token: Authorization: Bearer zap_live_…. See Authentication for key management and the alternate header.
Example request
curl https://zapinner.com/api/v1/execute \
-H "Authorization: Bearer zap_live_••••••" \
-H "Content-Type: application/json" \
-d '{"instruction":"clean up these messy customer records","data":{"company":" ACME, INC. "}}'request_id. Full field-level request and response schemas for this endpoint live in the OpenAPI spec and the API reference.Errors & limits
Errors use one consistent shape ( error.code, error.message, request_id). See Errors and Rate limits.
SDK
Execute has typed methods in both the JavaScript and Python SDKs. Both are implemented and package-ready but not yet published to npm / PyPI — until they ship, vendor the package source or install from a git ref, or call the endpoint over HTTPS with the example above.
Try it
Select Execute in the playground to see the request, or run it live with your API key.