set_proxy
Serve a backend at this subdomain through the AgentDomains edge, which terminates TLS with its own certificate — this is how you get working HTTPS on an origin that has no certificate of its own (a bare IP-less PaaS host, a tunnel, an internal box). Unlike a forward, the URL stays on your domain and the response is proxied, not redirected. Claims the label first if needed. Like a forward, a proxy TAKES OVER the hostname: A/AAAA/CNAME records on the label itself are deleted and returned in 'replaced_records', while sub-label and TXT records are untouched. A proxy and a forward are mutually exclusive on one label. Caveat: apps that hardcode their own hostname (OAuth callbacks especially) may need your new hostname registered on their side.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"label": "<label>",
"origin": "<origin>"
},
"name": "set_proxy"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| No | Email, if this call also claims a new name on an account without one. | ||
| label | Yes | The subdomain label, without the domain suffix (e.g. 'myapp' for myapp.makes.fyi). | |
| domain | No | Which domain to act under: 'makes.fyi' (the default) or 'agentdomains.co'. The same label can exist under each, so pass this whenever you are not using the default. | |
| origin | Yes | Backend hostname to proxy to, without a scheme (e.g. myapp.fly.dev). Must be a hostname, not an IP. |