integration.executeIntent captured
MODEL-INDEPENDENT / SUPERVISED API-WRITE GATEWAY
Put a supervised API-write boundary between AI intent and a real system write. ActionDock enforces destination, network, method, and path policy, binds the exact resolved target, query, and body into the approval preview, executes with a server-held credential, and returns an execution receipt.
integration.executeIntent captured
destination · method · pathPolicy allowed
owner.approvalRequest approved
provider.requestProvider responded
job + provider responseReceipt recorded
Intent → deterministic policy → owner approval → execution receipt
THE SUPERVISED WRITE CONTRACT
ActionDock is the API-write boundary between an existing agent and a compatible public REST API. It is designed for low- to moderate-volume changes that deterministic policy and a person should clear before execution.
The agent calls integration.execute with a connection, method, path, query, and body. It receives a job reference—not the credential behind the connection.
ActionDock enforces destination, method, path, network, and execution limits on the server. It then binds the connection version, resolved target, and exact query and body into the transaction preview. The model does not decide whether its own request is allowed.
A signed-in workspace owner reviews the exact transaction preview. Execution stays bound to the request version the owner approved.
Only ActionDock sends the approved request with the server-held bearer token or API key. The agent never receives the secret.
The receipt includes execution state, timestamps, request metadata, provider response, and error details. If the provider may have accepted a request but its response was lost, the job becomes execution_unknown: blind retry stays blocked, and an operator must reconcile downstream state before deciding what happens next. The receipt is an execution record, not proof that the business outcome completed.
START WITH THE WRITE STILL BLOCKED BY HAND
Start with a specific POST, PATCH, PUT, or DELETE that an agent can prepare but cannot safely execute today. Keep every supporting read or analysis subordinate to that transaction.
Put deterministic policy, exact-request approval, credential brokering, and an execution receipt around one real change.
READ ↗02 / CONTROLVisible execution stateTrack the approval state, provider response, and errors for the proposed change.
READ ↗03 / PREPAREStructured input and checksExtract fields and apply explicit rules before the agent proposes a write.
READ ↗04 / SUPPORTDocument evidenceAnalyze supplied material when a contract, policy, or request informs the change.
READ ↗05 / SUPPORTResearch and handoffGather source links or create a report when the reviewer needs more context.
READ ↗ONE WRITE PATH + SIX SUPPORTING ACTIONS
integration.execute is the product’s primary operation. The other six MCP and HTTP actions prepare, check, or document the transaction; they are not the product boundary by themselves.
Submit one bounded API write for owner review, then record the provider response.
CORE WRITERead from a permitted HTTPS method and path before or after the change.
SUPPORTING READPrepare caller-defined fields with supporting evidence.
SUPPORTINGApply explicit rules and return machine-readable failures.
SUPPORTINGCreate a cited brief from supplied business text.
SUPPORTINGResearch a bounded question with source links.
SUPPORTINGPersist a Markdown or JSON handoff artifact.
SUPPORTINGFIRST SAFE WRITE / LOCAL SIMULATION
Run integration.execute, inspect the exact transaction preview, and simulate owner approval. This local demo never contacts a provider or changes external data.
Public REST APIs with bearer-token or API-key authentication; low- to moderate-volume writes that a person reviews.
FIXED SAAS SUBSCRIPTIONS
Every plan includes the complete action catalog, API keys, approvals, workflow history, signed callbacks, and a monthly processing guardrail. There are no automatic overage charges and no purchasable usage balance.
Monthly or annual checkout.
Methods, paths, and secrets stay server-side.
All seven actions are included.
Work pauses at the monthly guardrail.
A first production agent workflow.
Owner-approved destinations and credentials.
Full action catalog, processing guardrail, and email support.
Several internal systems and workflows.
More approved systems under one workspace.
Higher processing guardrail and priority support.
Broad agent operations across a team.
Wider system coverage with the same controls.
Highest processing guardrail and rollout review.
Custom security, support, and deployment scope.
Exact scope and price disclosed before purchase.
Security review, onboarding, and support scope. Download pricing guide ↗
New jobs pause until the next subscription period or a plan upgrade. ActionDock never creates an automatic overage charge.
ActionDock is not a communications, marketing, social-posting, payment-processing, media-generation, or autonomous decision service.
Yes. Manage the subscription in the customer portal. Paid access continues through the applicable billing period unless the portal states otherwise.
YOUR FIRST SAFE WRITE