Skip to main content
Your TEE contract does not declare which hosts it may call. A tenant contract’s outbound HTTP egress is resolved, on every call, from the calling user’s authorization grant — the allowed hosts the user grants when they delegate to your agent or contract:
  • Delegated call → the subject user’s grant.
  • Direct (self) call → the caller’s own self-grant.
  • Call from another contract → the same grant as the original caller. A tenant contract reached over contracts-call never reaches more than the user behind the call granted.
If the target host (for example api.example.com) isn’t on the grant’s allowed-hosts list, the contract still runs but the outbound call is denied with host/http.egress_denied.
This is the most common reason a working contract can’t reach its API: the code is fine, but no grant authorizes the host. Set the grant before you invoke — see Member Delegation and Delegate access.
A grant is necessary but not always sufficient. Whatever the grant says, the node also holds every contract HTTP call to:
  • Public addresses only. A host that is private, loopback or a cloud-metadata address — or a name that resolves only to such addresses — is refused, even if the grant lists it.
  • A time limit and a size limit. By default a call must finish within 30 seconds and its response body must be no larger than 10 MiB; otherwise it fails (host/http.response_too_large for the body). The operator sets these limits, and neither can be changed from the contract or the grant.
See Common errors for the exact messages.