HTTP proxy
One path per binding. Point curl, a script or a CI job at it and the key goes on at our end.
Not everything that needs a key is an agent with an MCP client. A shell script, a cron job and a CI stage all get the same treatment through the reverse proxy.
Make a call
curl -X POST https://gw.sallyport.cloud/p/bnd_01J…/v1/refunds \
-H "Authorization: Bearer sp_live_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx" \
-d amount=4200 -d currency=usdThe bearer names your agent identity. The binding decides the upstream host, the path prefix and the methods. The credential is put on at our end and never travels back to you.
When a call needs a person
The proxy answers 202 with the call id and the approval URL in the body and in headers. Repeat the same request with the call id header once the card is answered, and you get the upstream response.
Bodies
| Limit | Value |
|---|---|
| Request body through the proxy | 512 MiB, streamed, chunked |
| Stored response | 8 MiB kept, the rest by reference |
| Returned inline | 256 KiB plus a handle |
A redirect that would carry your credential to another host stops here. The 3xx comes back to you as the result, and the gateway does not follow it with your key attached.