Bind the real approval.
Your trusted backend signs the order identity, customer and approved total. HALTSEAL returns one business ID. Agents cannot create funding or choose another customer’s budget.
Labs · AI execution · Local developer preview
One job.
One budget.
Keep the approved budget with the same AI job. Across retries, agents and provider changes.
A lost response does not prove a job failed. HALTSEAL keeps its maximum possible cost reserved, recovers the original job and settles from final cost evidence.
RC15.3 candidate · Python + JavaScript/TypeScript · Free SDK downloads · Full local evaluation by request
ORDER / ONE APPROVED BUDGETSYNTHETIC
Approved$20
- Provider A · reply lost
- $12 reserved
- Available for another job
- $8
- Provider B · needs $12
- HOLD
A new provider uses the same budget.
See how recovery releases capacityFor teams shipping paid AI workflows
The costly moment is the uncertain one.
Video and image applications can lose an acceptance response while a paid job is already running. Switching providers or starting another attempt can add cost to the same customer order.
Reserve before sending.
The gateway owns reservation and provider dispatch. A lost reply, new key or process restart keeps unresolved exposure attached to the original business.
Find the original job.
Read-only recovery matches the original execution and provider account. Only qualified final cost evidence releases unused capacity.
Best fit: a server-side approval source, paid asynchronous jobs and a provider that can establish a cost ceiling, original-job recovery and final billing. Direct calls that bypass the gateway remain outside its control.
Why this problem matters
Magic Hour’s integration guide warns that a timeout before a project ID can still leave a paid job running, and repeating the call can create another billable job. Blotato’s agent workflow guide tells agents to stop after submitting a paid job until its outcome is checked.
Magic Hour integration guide (opens in a new tab) · Blotato agent workflow guide (opens in a new tab)
Public workflow guidance, reviewed October 6, 2026. These companies are not presented as HALTSEAL customers. The guidance does not quantify a customer’s financial loss or establish willingness to buy.
Follow one budget
Uncertainty holds capacity.
Evidence releases it.
This browser illustration follows the same synthetic $20 scenario as the authorized local HTTP demo. It makes no API calls and spends no money.
- A accepts. Its reply disappears.The $12 ceiling remains reserved. Another $12 job is HOLD.
- Recover A. Verify its final $4 cost.Settle $4 once and release $8. The available balance becomes $16.
- Explicitly recheck the held job.B can now reserve $12 and execute. Recovery itself never dispatches B.
SAME BUSINESS / USD
- Approved total
- $20
- Final consumption
- $0
- Unresolved maximum
- $12
- Available
- $8
Provider B: HOLD
A is UNKNOWN. The $12 maximum remains reserved.
This preserves a cost envelope. A separate, permitted job capped at the remaining $8 could fit while A is unknown. It is not a guarantee that every distinct attempt has only one effect.
Start with the interface
Install the SDKs.
Evaluate one workflow.
Download the Python and JavaScript/TypeScript SDKs and inspect the API contract. Use them from your backend with an authorized local evaluation gateway.
Python 3.11+ · Node 22+ · MIT SDK licenses · Preview packages are direct downloads, not registry releases
From the folder containing your downloaded SDK archives
python3 -m pip install --no-index --no-deps ./haltseal_execute_sdk_preview-0.1.0rc3-py3-none-any.whl
npm install --ignore-scripts ./haltseal-execute-sdk-preview-0.1.0-rc.3.tgzInstalling a client package does not provide a running gateway or create an account. Read the SDK license.
Request the complete local evaluator.
The authorized evaluation package includes the gateway, two separate local provider fixtures, the SDKs and full reproduction tools. Reproduce the $20/$12/$4 flow, duplicate recovery, concurrent requests and actual process-kill boundaries. All provider costs are synthetic.
Request a local evaluation packageProvided through an agreed technical review. Requirements: POSIX Linux, Python 3.11+, Node 22+, npm and pip. Core engine source and operational materials remain within that review. Evaluation does not grant a production service license.
One execution boundary
Your app supplies the job.
The gateway owns the send.
A trusted order service imports a signed approval. Your backend passes the returned business ID to a customer-bound agent key. The provider credential stays with the gateway.
Python · local fixture example
from haltseal_sdk import Client
client = Client("http://127.0.0.1:8787", customer_key,
allow_loopback_http=True)
execution = client.execute(
business_id=business_id,
attempt_key="render-1",
connection_id="lab",
action="lab.fixed_job.v1",
parameters={"prompt": "Synthetic square"},
max_cost_micro="12000000",
)
# Recover the existing execution, never send directly.
observed = client.recover(execution["id"])JavaScript / TypeScript · local fixture example
import { Client } from "@haltseal/execute-sdk-preview";
const client = new Client({
baseUrl: "http://127.0.0.1:8787", apiKey: customerKey,
allowLoopbackHttp: true
});
const execution = await client.execute({
business_id: businessId, attempt_key: "render-1",
connection_id: "lab", action: "lab.fixed_job.v1",
parameters: { prompt: "Synthetic square" },
max_cost_micro: "12000000"
});
const observed = await client.recover(execution.id);These snippets assume a running configured local gateway, an imported approval and its execute key. The authorized local evaluation package creates them. HTTPS is required outside explicitly enabled literal loopback evaluation. USD amounts use integer micro-unit strings.
Same attempt, same result.
Keep the business ID and attempt key. An identical gateway request retrieves its existing execution. Changing the economic request under the same key conflicts.
Lost the gateway response?
Look up the same business ID and attempt key. If the execution is not yet visible, keep that identity and repeat only the identical gateway request. A transport timeout is not permission to call the provider again.
Recovery is read-only.
Recover the original execution. A verified final cost settles once. A held successor needs explicit resume and fresh checks. Cancellation alone does not refund exposed work.
OpenAPI contractEndpoint and error guideApproval and recovery contractPython wheelJavaScript / TypeScript package
From the folder containing your two downloaded SDK archives
python3 -m pip install --no-index --no-deps ./haltseal_execute_sdk_preview-0.1.0rc3-py3-none-any.whl
npm install --ignore-scripts ./haltseal-execute-sdk-preview-0.1.0-rc.3.tgzVersioned direct downloads. These preview packages are not published to PyPI or npm. Installation commands and timeout handling. Public download manifest.
Evidence attached to this release
Reproducible locally.
Provider qualification comes next.
The current package is RC15.3 candidate / Managed API 0.1.0-rc.3. Its local checks exercise authenticated approvals, real local HTTP, SDK installation, concurrent requests, lost replies and recovery.
116 / 116Local tests passed
16Actual SIGKILL boundaries passed
2 SDKsInstalled in clean directories
Available in this preview
- Signed order approvals and customer-bound access
- Approved budget shared across controlled jobs
- Original-job recovery and final-cost settlement in separate local fixtures
- OpenAPI and MIT SDK downloads, with the full evaluator available by request
Required before managed use
- A binding native-provider cost ceiling, original-job lookup and billing finality
- Qualified hosted operations, secret handling and customer isolation
- Account onboarding, real checkout and agreed service terms
- Customer-workflow validation and independent reproduction
No native AI execution, paid hosted endpoint or measured availability SLA is offered here. Local qualification does not establish production reliability. Existing Payment R2/C2 evidence remains separate.
Trust and deployment boundaries
Your trusted order system must identify the real work and sign its cumulative approval. HALTSEAL cannot infer that two different source order IDs secretly describe the same job. Agent keys cannot import approvals or assign themselves another customer’s funding.
This is single-host local evaluation. Backup restoration, joint-history rollback and host migration are not qualified. Existing RC2 databases are refused; no automatic history migration ships. Preserve historical consumption and unresolved work through any separately reviewed cutover. Operator recovery procedures accompany the evaluator under agreed technical-review scope.
The provider’s contract must establish the maximum bill and finality of evidence. A price estimate, completed job, empty lookup or cancel response alone is insufficient. fal remains a qualification candidate; its native dispatch is disabled.
Evaluate one paid AI workflow
Bring the uncertain job.
Agree the next decision.
Review one provider, one order approval source and one failure path with Scott Lee, founder and author. First determine whether your provider can support the required cost and recovery contract.
An inquiry does not activate a service or authorize paid work. Scope, fees, provider support and terms are agreed before an engagement.
Useful for the first conversation
- Your product, AI provider and who approves the job budget.
- What happened after a timeout, retry or provider change.
- The engineering owner, budget owner and next decision.
Start with non-confidential context. Keep API keys, personal data and raw invoices out of the inquiry form. Any permitted, redacted order/job/billing evidence is reviewed later through an agreed channel.