Valta Docs
Financial-Action Proxy
Valta's proxy is a financial-action egress gate, available at POST /api/v1/proxy. It is designed for supported service calls that should pass through an agent wallet and spending controls. It is not an OpenAI-compatible LLM proxy.
Request flow
- Your server or agent client authenticates to Valta with a Valta API key.
- The caller identifies the agent, a supported service, a relative path, HTTP method, declared amount, and description.
- Valta checks the agent's wallet and spending controls.
- If the spend is approved, Valta forwards the request to the fixed origin configured for that service, using the account's stored provider credential.
- Valta returns the provider's HTTP status and response body.
The proxy accepts only relative paths beginning with /; it does not accept a caller-supplied full destination URL. Only services with a configured proxy origin can be forwarded.
What the amount means
The caller supplies the amount that Valta checks against the wallet. Valta does not independently calculate the provider's eventual charge from the request or response body. If the caller understates the amount, the recorded spend can be inaccurate.
If a spend check denies the request, the outbound provider call is not made. The wallet spend path also denies a request when it cannot verify configured daily or monthly spend totals. This is specific to the financial-action proxy path, not a claim that all provider calls made by an agent are automatically routed through Valta.
Receipts and request bodies
The proxy receipt stores metadata such as agent, service, method, path, declared amount, decision, reason, provider response status, description, and creation time. The receipt table does not contain request-body or response-body columns.
Receipt persistence is best-effort in the current implementation. A database error while inserting a receipt is swallowed, so the receipt list should not be treated as a guaranteed record of every attempted call. No receipt-retention period is published.
Next steps
- Follow the Proxy Setup guide to configure credentials and send a request.
- Read Key Safety and Proxy Data for credential storage, logging details, and limitations.