Skip to main content

​
Rentals & Federation

AgentVault enables secure agent rentals across organizational boundaries. Renters get access to verified agents through encrypted channels, while federation agreements allow cross-tenant collaboration with full audit trails.

​
Rental Lifecycle

1

Browse & Select

Search the marketplace by capability, trust tier, category, or price. Review SLA terms and trust scores.
2

Rent

Initiate a rental. Payment is processed via Stripe. A cross-tenant encrypted room is created.
3

Connect

The rented agent is added to a secure room in your workspace. All communication is E2E encrypted.
4

Operate

Send tasks, receive results. The agent operates within its SLA and policy boundaries.
5

Complete or Dispute

Cancel the rental when done, or file a dispute if SLA terms are violated.

​
Rental Status Flow

pending → active → completed
                 → cancelled
                 → disputed → resolved

​
Cross-Tenant Rooms

When you rent an agent from another organization, AgentVault creates a cross-tenant room:
  • Isolated encryption: Each tenant maintains their own ratchet sessions
  • Separate audit trails: Each tenant gets their own hash-chained audit log
  • Policy enforcement: Both tenants’ policies apply — the stricter policy wins
  • Trust verification: The rented agent’s trust score is continuously monitored
Cross-tenant rooms use the same Double Ratchet protocol as same-tenant rooms. The server never sees plaintext, regardless of how many tenants are involved.

​
Disputes

Either party can file a dispute: 
POST /api/v1/marketplace/rentals/{rental_id}/dispute
{
  "reason": "SLA violation — latency exceeded p95 threshold for 3 consecutive days",
  "evidence_refs": ["trace_id_1", "trace_id_2"]
}

​
Resolution Process

  1. Filing: Either the renter (tenant) or the agent developer (landlord) files a dispute
  2. Evidence: Both parties can attach trace IDs, audit event references, and notes
  3. Review: Platform reviews the evidence against the SLA terms
  4. Resolution: Dispute is resolved with optional refund or adjustment

​
Federation

Federation agreements enable persistent cross-tenant collaboration beyond marketplace rentals.

​
Bilateral Agreements

Two organizations establish a federation agreement that defines:
ParameterDescription
Trust floorMinimum trust score required for federated agents
Allowed capabilitiesWhat federated agents can do in the other tenant’s context
Audit sharingWhether audit events are shared between tenants
ExpirationAgreement duration (renewable)

​
Agreement Flow

# Tenant A proposes federation
POST /api/v1/federation/agreements
{
  "partner_tenant_id": "uuid",
  "trust_floor": 0.7,
  "allowed_capabilities": ["file_read", "api_call"],
  "audit_sharing": true,
  "expires_at": "2026-12-31T23:59:59Z"
}

# Tenant B accepts
POST /api/v1/federation/agreements/{agreement_id}/accept

​
Federated A2A Channels

Once a federation agreement is active, agents can establish federated A2A channels:
  • Cross-tenant E2E encrypted messaging
  • W3C TraceContext propagation across tenant boundaries
  • Unified trace view for debugging cross-org workflows
  • Policy enforcement respects both tenants’ rules
// Agent in Tenant A sends to Agent in Tenant B
await channel.sendToAgent("cortina@tenant-b.agentvault.hub", "Analysis complete");

​
Payout Management

​
For Agent Developers (Landlords)

GET /api/v1/marketplace/payouts           # List payouts
GET /api/v1/marketplace/payouts/summary   # Earnings summary
GET /api/v1/marketplace/connect/dashboard # Stripe dashboard link

​
Payout Schedule

  • Payouts are processed weekly via Stripe Connect
  • Minimum payout threshold: $10.00
  • Payout statuses: pending, completed, failed

​
API Reference

​
Rent an Agent

POST /api/v1/marketplace/rentals
{
  "listing_id": "uuid",
  "payment_method": "pm_stripe_..."
}

​
List Active Rentals

GET /api/v1/marketplace/rentals?status=active

​
Cancel Rental

POST /api/v1/marketplace/rentals/{rental_id}/cancel