API Reference
The UGTP REST API provides read-only access to protocol status, contract metadata, chain configuration, and fee information.
Base URL
All endpoints return JSON responses. No authentication is required for read-only endpoints.
Endpoints
/api/healthReturns the health status of the UGTP API, including uptime and timestamp.
Example
curl.exe -s #a5d6ff">"https://api.ugtp.net/api/health"{
"status": "healthy",
"timestamp": "2025-06-15T12: 00: 00.000Z",
"uptime": 86400
}/api/versionReturns the current protocol version and API version.
Example
curl.exe -s #a5d6ff">"https://api.ugtp.net/api/version"{
"protocol": "0.1.0",
"api": "1.0.0",
"status": "beta"
}/api/chainsLists all blockchain networks supported by the protocol, including chain IDs and RPC endpoints.
Example
curl.exe -s #a5d6ff">"https://api.ugtp.net/api/chains"{
"chains": [
{
"chainId": 43114,
"name": "Avalanche C-Chain",
"rpcUrl": "https://api.avax.network/ext/bc/C/rpc",
"explorer": "https://snowtrace.io",
"status": "active"
}
]
}/api/contractsReturns the addresses of all deployed protocol contracts on each supported chain.
Example
curl.exe -s #a5d6ff">"https://api.ugtp.net/api/contracts"{
"chainId": 43114,
"contracts": {
"ProtocolConfig": "0x42E2fc8a7fd49225626616404009809247B652d1",
"PolicyHook": "0x6B90ef95AfF97d0164E341DBf155c6750408cdCc",
"UCIRegistry": "0xF7714385c5762db4060865367e790949C3AfF2de",
"UCARegistry": "0xCcD3720336Ce37311Db054BF0cACB66F79f661ac",
"LinkedAccountRegistry": "0x09660060f753D19cF210abb3B883F487914EE116",
"IntentRegistry": "0x2cE0955fF70c68ECae7417142E9c96E69aDdE212",
"AdapterRegistry": "0xCa6117092E02cf8C41C080dFa911884F83F58443"
}
}/api/feesReturns the current fee configuration for protocol operations.
Example
curl.exe -s #a5d6ff">"https://api.ugtp.net/api/fees"{
"chainId": 43114,
"fees": {
"registration": "0",
"intentSubmission": "0",
"currency": "AVAX"
},
"note": "Fees are waived during beta"
}Rate Limiting
The API currently has generous rate limits during the beta period. In production, rate limits will be enforced per IP address. Standard limits are expected to be approximately 100 requests per minute. Responses include rate-limit headers when limits are approached.
Error Responses
All error responses follow a consistent format:
{
"error": {
"code": "NOT_FOUND",
"message": "The requested resource was not found"
}
}| Status | Meaning |
|---|---|
| 200 | Success |
| 400 | Bad request — malformed parameters |
| 404 | Resource not found |
| 429 | Rate limit exceeded |
| 500 | Internal server error |