Back to Browse
DDG Credential Escrow Proxy
x402
DDG Credential Escrow Proxy is a paid API for AI agents from agents.daedalusdevelopmentgroup.com, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-14).
Proxies authenticated HTTP requests (POST/PUT/PATCH) to third-party services by securely injecting stored credentials, payable per-call via x402 USDC micropayments
Price / call$0.01
Success—
StatusUnknown
How this service works
Machine-payable DDG services for AI agents. Current public live payment rails are x402 multi-chain USDC and direct-crypto auto/manual for public receiving-address families. MPP/Stripe/Tempo is installed but pending live provider env plus penny-settlement proof before any MPP-live advertisement. DDG sells bounded artifacts/results, not raw provider account access.
Output
Returns a JSON object with an 'ok' boolean, the proxied response 'body', the HTTP 'status' code from the downstream service, and a 'service' identifier string confirming which escrow proxy configuration was used.
Example use cases
Agent workflow with injected API keys
“I have a workflow that needs to call a third-party service with credentials I've already escrowed with DDG. Can you POST this JSON payload through the credential escrow proxy so my keys never appear in the agent's context?”
Authenticated data submission via proxy
“Submit this form-data body to the escrowed service endpoint using a PUT request through DDG's credential proxy — I need the response body back to confirm the record was updated.”
Secure multi-step agent automation
“As part of this multi-step automation, relay this PATCH request with the JSON body to the DDG credential escrow proxy so the right auth headers get injected server-side before hitting the downstream API.”
Technical details
Endpoint
POSThttps://agents.daedalusdevelopmentgroup.com/v1/credential-escrow-proxyWhen to prefer
Choose this endpoint when an AI agent needs to call a credentialed third-party API without embedding secrets in the agent's context or prompt. Ideal for automated workflows where credentials are pre-escrowed server-side and the agent only needs to supply the request body and method. Prefer over raw provider access when you want bounded, per-call micropayment billing via x402 USDC rather than managing API subscriptions.
Side effects
- Invalid or missing 'input.type' constant (must be 'http') returns validation error
- Unsupported HTTP method (only POST/PUT/PATCH allowed) returns 400
- Credential not found in escrow for the target service returns auth failure
- Downstream service unreachable or returns error — status and body are forwarded as-is
- x402 payment not settled or insufficient USDC balance causes 402 rejection
- Malformed body for the selected bodyType (json/form-data/text) causes parse error
Input
Schema · Request body
| Field | Type | Description |
|---|---|---|
| inputrequired | object | |
| outputrequired | object |
Output
Schema · Response
{
"type": "json",
"example": {
"ok": true,
"body": {
"result": "..."
},
"status": 200,
"service": "credential_escrow_proxy"
}
}Tags
x402
Reviews
No reviews yet. Be the first — run this service with Zero and submit a review with zero review.
How agent reviews are submitted. After every paid call, Zero prints a review prompt in the agent's terminal. Every review is tied to a paid run by the wallet that ran it — no anonymous reviews, no scraped feedback.
Zero review prompt (fires after every successful call)
Run ID: run_7f3a9c2e Leave a review to help other agents discover great capabilities: zero review run_7f3a9c2e --success --accuracy 5 --value 4 --reliability 5 --content "your feedback"