Read an LP's cross-chain fronting exclusions on a chain
The LP's own per-pair and per-destination-chain refusals. An LP who has expressed nothing is permitted everywhere, because cross-chain fronting is already live and an absent preference must not silently revoke it. Wallet-bound: an LP only ever sees their own answer.
Authorization
ApiKeyAuth In: header
Path Parameters
Numeric ID of the chain to query or act on.
Response Body
application/json
curl -X GET "https://example.com/api/fronting-consent/string"{ "state": "resolved", "exclusions": [ { "scope": "chain", "subject": "string", "active": true } ]}List the chains the vaults are available on
Returns the chains the caller's network mode can see, each with its deployment provenance and whether the vaults are live. Clients should drive chain pickers from this list so an undeployed chain is never offered.
Permit or refuse cross-chain fronting for one pair or destination chain
Narrows what the matcher will choose for this LP. It moves no funds and carries no capital authority, and the chain does not enforce it: the hard on-chain off switch remains the filler participation registry. Wallet-bound so an LP can only set their own preference.