KOLIANCE
KOLIANCE DEVELOPER SPECIFICATION V1.0

Documentation & API Reference

The verifiable trust, dynamic neural agent cards, and cryptographic settlement layer on Monad parallel EVM.

1. Quickstart & Sandbox Testing

Developers can interact with Koliance via our RESTful BFF Gateway or directly query Monad smart contracts. To get started without billing credentials, every newly connected wallet receives 3 free Starter Claims (100 calls each).

Step 1: Test Market Query via Curl
curl -X GET "https://koliance.vercel.app/api/market?symbol=NVDA" \
  -H "Accept: application/json"
Sample JSON Output:
{
  "code": 200,
  "message": "Market quote retrieved successfully",
  "data": {
    "symbol": "NVDA",
    "price": 142.50,
    "source": "ALPACA_REALTIME",
    "timestamp": 1729761200
  }
}

2. Protocol Architecture & Monad Parallel EVM

Koliance is engineered to exploit the parallel execution pipeline and sub-second finality of Monad (Chain ID 10143). By segregating state writes across isolated account paths, high-frequency AI agent settlements and dynamic attestation mints bypass typical EVM gas spikes and mempool contention.

Cryptographic Identity Layer

Dynamic neural Agent Cards attest Web3 wallet activity, GitHub commit velocity, and Steam achievements into deterministic on-chain trust scores.

Autonomous Settlement Rails

Perpetual contract positions, oracle aggregation (Pyth & Alpaca), and session-delegated transaction batching provide sub-second solvency validation.

3. EIP-712 Session Key Delegation

To allow AI agents to trade and consume computational resources without holding primary private keys or prompting manual wallet signatures, Koliance enforces typed structured EIP-712 session key delegations via SessionKeyRegistry.sol.

Strict Cryptographic Security Constraints:
  • • maxPerTxUSD: Strict single-transaction expenditure ceiling.
  • • dailyLimitUSD: 24-hour rolling cumulative consumption cap.
  • • allowedMCCs: Whitelisted Merchant Category Codes / Smart Contract methods.
  • • Emergency Circuit Breaker: Account owners can freeze or revoke session keys instantly on-chain.

4. Developer API Reference

All API endpoints accept JSON payloads and authenticate via the x-api-key request header or EIP-712 bearer signatures.

GET/api/market

Fetch live price quotes, 24h change, and Pyth / Alpaca oracle status.

Parameters: symbol (e.g. NVDA, AAPL, BTC, ETH)
GET/api/console/api-keys

Query remaining API quota, tier status, active session keys, and 24h volume.

POST/api/v1/settlement/commit

Commit an autonomous agent payment transaction with Monad block receipt validation.

5. Smart Contracts & Monad Testnet Addresses

The authoritative trust registries and settlement contracts deployed on Monad Testnet (Chain ID 10143):

ContractAddress on Monad TestnetExplorer
Koliance Core Trust Registry0x6291C790dbB41198c69781B2B7a01d674843b0C5View
SessionKeyRegistry (EIP-712)0xCb7f01F6E9B9b33aC5161FEaA28eB8Ce3b5fB09DView
PositionManager (Perp Engine)0x3fCeD0662657e0C3a2aF8A80e3A4cDb8A7d1d2C4View

6. Standardized Error Handling (ADR-006)

In compliance with architectural decision record ADR-006, all gateway errors return closed-set status codes with machine-parseable error descriptors:

400 Bad Request:

Malformed parameter, invalid signature, or zero address.

401 Unauthorized:

Missing or expired API key or invalid session signature.

429 Rate Limit Exceeded:

Exceeded tier RPM limit (60, 300, or 1,200 RPM).

503 Service Unavailable:

Upstream RPC degradation or Go gateway unreachable.