QuoteSeal

Product flow

Describe - Seal - Buy / Block / Raise

The live diagram tracks your chat: allowed quotes pay, overspend is blocked, and raising the seal always needs a new approval.

Kite · Passport

Identity is part of the product

QuoteSeal runs sealed spends under hard caps, with Kite Passport as the verifiable agent identity rail when available on the host.

1. 01 · Identity

   Verifiable agent identity

   Status from /api/kite/status surfaces agent id, login, and session. Approve can request a Passport spending session with passkey approval when the host is connected.

2. 02 · Limits

   User-defined permissions

   You set total budget and max per quote, approve the seal once, and pay-time code refuses anything above it. Raising always needs a new approval - never a silent escalate.

3. 03 · Payments

   Sealed quote network

   Buys run against the quote network under the seal (buy / block / raise). When Passport is connected, Approve also opens a spending session for passkey confirmation.

For developers

Agent and API notes

Always-on integrator surface: curls, env names (no secrets), OpenAPI, and optional MCP. Product chat above stays jargon-free.

# QuoteSeal health - OpenAPI: $BASE_URL/openapi.yaml
curl -s "$BASE_URL/api/health"

# QuoteSeal mandate - free text to sealed plan
curl -s -X POST "$BASE_URL/api/mandate" \
  -H 'Content-Type: application/json' \
  -d '{
    "message": "Get up to 3 quotes for a 40 m2 solar-film install in Lyon. Total budget 3 USDC. Max 1 USDC per quote. Valid for 2 hours."
  }'

# QuoteSeal sealed run - pass MandatePlan from /api/mandate
# Tip: PLAN=$(curl -s -X POST "$BASE_URL/api/mandate" -H 'Content-Type: application/json' \
#   -d '{"message":"40 m2 solar film in Lyon, 3 USDC total, 1 USDC max per quote"}')
# curl -s -X POST "$BASE_URL/api/run" -H 'Content-Type: application/json' -d "{\"plan\": $PLAN}"
curl -s -X POST "$BASE_URL/api/run" \
  -H 'Content-Type: application/json' \
  -d '{
    "plan": {
      "mandate": {
        "job": "solar film install",
        "city": "Lyon",
        "areaM2": 40,
        "maxQuotes": 3,
        "maxAmountPerTx": 1,
        "maxTotalAmount": 3,
        "ttlHours": 2,
        "preferredTiers": ["cheap", "standard", "premium"]
      },
      "session": {
        "taskSummary": "Sealed quote run",
        "maxAmountPerTx": 1,
        "maxTotalAmount": 3,
        "ttlHours": 2,
        "assets": "USDC",
        "allowedEndpoints": [
          "$BASE_URL/api/x402/quote/cheap",
          "$BASE_URL/api/x402/quote/standard",
          "$BASE_URL/api/x402/quote/premium"
        ],
        "mode": "kite_sandbox"
      },
      "plan": [
        { "tier": "cheap", "reason": "Under seal", "expectedPriceUsdc": 0.3 },
        { "tier": "standard", "reason": "Under seal", "expectedPriceUsdc": 0.8 },
        { "tier": "premium", "reason": "May block", "expectedPriceUsdc": 1.5 }
      ],
      "rationale": "Agent sealed plan",
      "source": "fallback"
    }
  }'

# Quote network merchants (402 without X-PAYMENT; seal enforced with session token)
curl -s "$BASE_URL/api/x402/quote/cheap"
curl -s "$BASE_URL/api/x402/quote/standard"
curl -s "$BASE_URL/api/x402/quote/premium"

For agents

Call QuoteSeal before you spend on quotes.

QuoteSeal is a sealed spending gate for quote buys - not an open wallet. Other agents POST here to compile a plan, approve a seal, then buy only under the cap. Humans use the chat above; agents use the same REST surface (and optional MCP) to get buy / block / raise events without silent escalate. Passport identity lives under /api/kite/*. See Identity for live agent status and session create.

Environment (no secrets in chat or commits):
- SERV_API_KEY optional - without it, mandate compile uses a local parser
- SERV_BASE_URL defaults to the OpenServ inference API
- NEXT_PUBLIC_APP_URL - public origin for x402 resource URLs
- QUOTESEAL_BASE_URL - MCP proxy target (default https://quoteseal.ozc.fr)
Copy .env.example to .env.local. Never commit .env.local.

# QuoteSeal health - OpenAPI: $BASE_URL/openapi.yaml
curl -s "$BASE_URL/api/health"

# QuoteSeal mandate - free text to sealed plan
curl -s -X POST "$BASE_URL/api/mandate" \
  -H 'Content-Type: application/json' \
  -d '{
    "message": "Get up to 3 quotes for a 40 m2 solar-film install in Lyon. Total budget 3 USDC. Max 1 USDC per quote. Valid for 2 hours."
  }'

# QuoteSeal sealed run - pass MandatePlan from /api/mandate
# Tip: PLAN=$(curl -s -X POST "$BASE_URL/api/mandate" -H 'Content-Type: application/json' \
#   -d '{"message":"40 m2 solar film in Lyon, 3 USDC total, 1 USDC max per quote"}')
# curl -s -X POST "$BASE_URL/api/run" -H 'Content-Type: application/json' -d "{\"plan\": $PLAN}"
curl -s -X POST "$BASE_URL/api/run" \
  -H 'Content-Type: application/json' \
  -d '{
    "plan": {
      "mandate": {
        "job": "solar film install",
        "city": "Lyon",
        "areaM2": 40,
        "maxQuotes": 3,
        "maxAmountPerTx": 1,
        "maxTotalAmount": 3,
        "ttlHours": 2,
        "preferredTiers": ["cheap", "standard", "premium"]
      },
      "session": {
        "taskSummary": "Sealed quote run",
        "maxAmountPerTx": 1,
        "maxTotalAmount": 3,
        "ttlHours": 2,
        "assets": "USDC",
        "allowedEndpoints": [
          "$BASE_URL/api/x402/quote/cheap",
          "$BASE_URL/api/x402/quote/standard",
          "$BASE_URL/api/x402/quote/premium"
        ],
        "mode": "kite_sandbox"
      },
      "plan": [
        { "tier": "cheap", "reason": "Under seal", "expectedPriceUsdc": 0.3 },
        { "tier": "standard", "reason": "Under seal", "expectedPriceUsdc": 0.8 },
        { "tier": "premium", "reason": "May block", "expectedPriceUsdc": 1.5 }
      ],
      "rationale": "Agent sealed plan",
      "source": "fallback"
    }
  }'

# Quote network merchants (402 without X-PAYMENT; seal enforced with session token)
curl -s "$BASE_URL/api/x402/quote/cheap"
curl -s "$BASE_URL/api/x402/quote/standard"
curl -s "$BASE_URL/api/x402/quote/premium"

{
  "mcpServers": {
    "quote-seal": {
      "command": "npx",
      "args": ["tsx", "mcp/server.ts"],
      "cwd": "/absolute/path/to/QuoteSeal",
      "env": {
        "QUOTESEAL_BASE_URL": "https://quoteseal.ozc.fr"
      }
    }
  }
}

FAQ

Frequently asked questions

Seal, SERV, Passport identity, agents - short answers.

• What is QuoteSeal?+

  A sealed quote-buying product for any job and any city. You describe the work, approve a hard spending seal (total budget and max per quote), then quotes are bought under that cap. Anything above the seal is blocked - raising the limit always needs a new approval.

• What is SERV Reasoning, and how is it different from the seal?+

  The seal is deterministic code: per-quote and total caps checked at pay time, never silently raised. SERV Reasoning (OpenServ) is optional judgment for turning free-text into a mandate plan and for raise-ask copy when a quote would exceed the seal. If SERV_API_KEY is unset, a local parser keeps plans reproducible. Rules stay in code; SERV does not override a block.

• Is this real money? What about Kite Passport?+

  Safety note: quote-network offers on this host do not move real funds unless you explicitly approve a Passport spending session. Kite Passport is the identity and session rail - see #kite for live agent status. Neither QuoteSeal nor SERV custodies funds or keys.

• How does QuoteSeal map to the Kite track?+

  Three pillars: (1) verifiable identity - Passport agent id and session status via /api/kite/* and the Identity section. (2) user-defined permissions - the seal enforces total + max per quote at pay time, no silent raise. (3) agentic payments - sealed buys against the quote network; Approve can open a Passport session when the host is connected.

• How does Approve work?+

  After the assistant compiles your request into a plain-English seal, nothing is spent until you click Approve and buy. That creates a short-lived sealed session with the same per-quote and total caps. When Passport is connected on the host, Approve also requests a Passport spending session and can show a passkey approval link. Each subsequent buy is checked against the seal at pay time.

• Why was a quote blocked?+

  A block means the quote price is above the per-quote seal, or paying it would exceed the total budget. QuoteSeal will not auto-raise. If a raise would help, the assistant can ask you to approve a new seal with higher limits - you stay in control.

• What jobs and cities are supported?+

  Any job, any city. Merchant names and EUR heuristics resolve from the job type (solar film, paint, HVAC, or generic local trade). Seal USDC prices stay fixed for predictable sealed runs: cheap 0.3, standard 0.8, premium 1.5.

• Can other agents call QuoteSeal?+

  Yes. See For developers (#developers) and For agents (#agents): OpenAPI at /openapi.yaml documents GET /api/health, POST /api/mandate, POST /api/run, /api/kite/*, and the quote network. Optional MCP: npm run mcp with QUOTESEAL_BASE_URL.

• What is the MCP / integrator path?+

  Agents can compile a mandate, show the seal to a human, then run sealed buys. Prefer the live base URL https://quoteseal.ozc.fr. OpenAPI and the Agents section include ready-to-copy curls and Cursor MCP config.

• Where does the left tip bubble near the chat button come from?+

  The floating Ask QuoteSeal button occasionally shows a short tip to its left after the intro finishes. It pauses while you are typing in the main assistant on mobile, stops after you open help twice dismissed, and never spends money - it only opens product help.

• Is this financial or purchasing advice?+

  No. QuoteSeal is a spending-seal product for quote buys under a hard cap, not a recommendation of vendors, prices, or contracts. Review every plan before you approve.