Parliament.
Deliberation as a service.

Why four voices?

This design is based on KALEI research on multi-agent parliamentary reasoning across frontier models. Read the Parliament paper →

Tiers

Quickstart

curl -X POST https://parliament.kaleiai.com/v1/parliament/standard \
  -H "Content-Type: application/json" \
  -H "X-PAYMENT: <base64 EIP-3009 authorization>" \
  -d '{
    "question": "Should I retry this failed payment once before escalating?",
    "context": "Payment processor is at 99.5 percent uptime. Retry cost is a new gas payment. No idempotency key available."
  }'

import { wrapFetchWithPayment } from 'x402-fetch';
import { privateKeyToAccount } from 'viem/accounts';

const account = privateKeyToAccount(process.env.AGENT_PRIVATE_KEY);
const fetchWithPayment = wrapFetchWithPayment(
  fetch,
  account,
  BigInt(1_000_000) // $1 max per call
);

const res = await fetchWithPayment(
  'https://parliament.kaleiai.com/v1/parliament/standard',
  {
    method: 'POST',
    headers: { 'Content-Type': 'application/json' },
    body: JSON.stringify({
      question: 'Should I retry this failed payment once?',
      context: 'Provider uptime 99.5%. Retry has a small gas cost.',
    }),
  }
);

const decision = await res.json();
// decision.synthesis.recommendation: "do_now" | "do_with_caveat" | "wait" | "abandon" | "needs_more_info"
// decision.synthesis.confidence: 0..1
// decision.synthesis.rationale: string
// decision.synthesis.minority_concern_to_address: string | null
// decision.synthesis.tripwire: string | null
// decision.votes: Array<{ personality, vote, confidence, reasoning, what_changes_my_vote }>

Response shape

On a successful payment, you receive HTTP 200 with a JSON body containing each voter's vote and reasoning, and the synthesizer's unified recommendation. The cheap tier omits the synthesizer and returns a majority tally instead.

{
  "tier": "standard",
  "question": "Should I retry this failed payment once before escalating?",
  "votes": [
    { "personality": "architect",  "vote": "yes",  "confidence": 0.78, "reasoning": "...", "what_changes_my_vote": "..." },
    { "personality": "engineer",   "vote": "wait", "confidence": 0.65, "reasoning": "...", "what_changes_my_vote": "..." },
    { "personality": "researcher", "vote": "yes",  "confidence": 0.82, "reasoning": "...", "what_changes_my_vote": "..." },
    { "personality": "pm",         "vote": "yes",  "confidence": 0.71, "reasoning": "...", "what_changes_my_vote": "..." }
  ],
  "synthesis": {
    "recommendation": "do_now",
    "confidence": 0.74,
    "rationale": "The two substantive yes votes converge on a low-risk retry pattern; the engineer's wait reflects a concern that should be logged, not blocking.",
    "minority_concern_to_address": "Engineer flagged potential for double-charging if the first attempt actually succeeded on the provider side. Check idempotency guarantees before retry.",
    "tripwire": "If provider returns success on retry AND we have no idempotency key, log a reconciliation alert for human review.",
    "vote_breakdown": { "yes": 3, "no": 0, "wait": 1, "abstain": 0 }
  },
  "duration_ms": 13218
}

Operational

Where does the money go?

Payments settle on Base mainnet directly to venelin.base.eth. Revenue funds KALEI research and the infrastructure that hosts Parliament (Anthropic API usage, Hetzner servers, Cloudflare edge).

What's logged?

Per-call anonymized metadata: tier, duration, recommendation, vote breakdown, question/context lengths. Request payloads are not stored. Payment proofs are not stored.

What if the service is down?

A failed payment never settles — the x402 facilitator rejects on verify and no USDC leaves your wallet. On upstream errors the service returns HTTP 500 with an empty body; retry with backoff is safe. A daily cost cap returns HTTP 503 if we exceed a safety threshold; this is rare but exists.

Rate limits

10 requests per second per source IP, 20 request burst. Paid requests are rate-limited the same as unpaid 402 challenges. Contact us if you need a higher limit for a specific use case.