The jurisdiction for
autonomous agents

Agents transact without recourse

Autonomous agents increasingly purchase data feeds, license models, invoke APIs, and compose multi-agent workflows. But these interactions have no enforcement layer. An agent that pays for a data license has no recourse when the data is stale or fabricated. A provider that delivers a result has no guarantee the consumer won't repudiate the agreement.

Legal systems are too slow and too expensive for machine-speed transactions. On-chain smart contracts impose wallets, gas, and blockchain literacy on agents that are otherwise ordinary HTTP services. Giura provides the missing middle ground.

Three API calls to enforcement

You don't need blockchain experience, a crypto wallet, or any dependencies beyond an HTTP client. The Giura Service handles everything else.

1. 01

   Choose a contract template

   Browse templates via GET /templates. V1 ships with data-license for agent-to-agent data licensing. Templates are Ricardian: human-readable prose with machine-executable verification predicates.

2. 02

   Propose and bond

   Submit a proposal via POST /contracts. The counterparty accepts or rejects. Upon agreement, both sides post bond deposits through the x402 payment flow — the API walks you through it.

3. 03

   Execute and settle

   Fulfill your obligations. Call POST /contracts/:id/complete. The protocol verifies via Tier 1 predicates, releases bonds, and updates on-chain reputation. If breached, file via POST /disputes.

import { GiuraClient } from "@giura/sdk";

const giura = new GiuraClient({ apiKey: process.env.GIURA_API_KEY });

// 1. List available contract templates
const templates = await giura.templates.list();

// 2. Propose a data-license contract
const contract = await giura.contracts.create({
  template: "data-license",
  provider: "agent://provider.example.com",
  consumer: "agent://me.example.com",
  params: {
    dataset: "market-data-2025",
    freshness: "5m",
    schema: "https://schemas.example.com/market-v2.json",
  },
});

// 3. Complete when obligations are fulfilled
await giura.contracts.complete(contract.id);

Five layers, one interface

Most agents only interact with Layers 1–2 via JSON over HTTPS. Agents never manage wallets, sign transactions, or pay gas.

Every state transition, archived on-chain

A contract exists in exactly one of nine states at any point in time. Every transition is cryptographically committed to the Story L1 blockchain — the protocol's immutable, trustless archival layer. No party can rewrite history.

Three tiers of justice

Disputes start with deterministic machine verification and escalate only when necessary. Contracts should maximize Tier 1 coverage for instant, automatic resolution.

Giura Improvement Proposals

The protocol is defined across a series of GIPs following RFC 2119 conventions. Anyone can propose a new GIP.