- 01Request
- 02Offer
- 03Obligation
- 04Approved Use
- 05Repayment
- 06Credit State
THE CREDIT LAYER FOR THE HUMAN–AGENT ECONOMY
Credit for the economy people and AI agents are building together.
IPO.ONE turns verified activity into a credit record that carries forward—so people and agents can access capital on clear terms, put it to work, repay, and build better access over time.
BORROW. BUILD. PROVE.
AGENT WORKING CAPITAL
How an AI agent gets working capital.
A Principal sets the Mandate. Capital providers set the terms. IPO.ONE records the obligation, approved use, repayment and verified outcome.
Illustrative product walkthrough
Principal verified
Principal record
- Relationship
- Owner / controller
- Authority state
- Active
- Review
- Current
Identity binding
Mandate
- Purpose
- Compute, data, approved APIs
- Aggregate budget
- $18,000
- Per action
- $4,000
- Providers
- Approved catalog
- Expiry
- 30 days
- Stop conditions
- Cap, expiry, revocation
Credit Request
Capital Offers
Obligation
Authorization
- Destination
- Approved provider catalog
- Purpose
- Compute + data + APIs
- Expires
- With Mandate
- Stop
- Cap or revocation
Approved Use
Repayment
Credit State
- Authorized by
- Verified Principal
- Permitted
- Identity-bound request preparation
- Prohibited
- Self-granted authority
- Current object / result
- Principal verification record
TWO ENTRY MODES
Two interfaces. One credit system.
Human and Agent journeys begin with different authority and converge on the same Offer, Obligation, repayment and Credit State.
VERIFIED PERFORMANCE
A settled outcome becomes useful credit history.
Credit Passport is a permissioned view of selected Evidence—not a public profile and not a universal score.
Limited history
- Indicative capacity
- $18,000
- Indicative tenor
- 30 days
- Credit Tier
- Emerging
Obligation settled
- New Evidence
- Repayment + execution
- Indicative access
- $24,000 · 45 days
- Credit Tier
- Established
Only the selected recipient and purpose may receive the approved Evidence set.
- Identity assurance Included
- Obligation history Included
- Repayment performance Included
- Execution quality Included
- Mandate compliance Included
- Evidence provenance Included
- Credit Tier Included
CAPITAL PROVIDERS + RAILS
Capital providers set the terms.
IPO.ONE coordinates the request, Offer, Obligation, settlement Evidence and credit history while each provider retains its economic decision.
One Obligation remains fixed while the selected execution rail changes.
- Accepted amount
- $18,000
- Total due
- $18,540
- Selected rail
- Bank
- Credit history
- One continuous record
DEVELOPERS + TRUST
One lifecycle, available through every interface.
Human interfaces, REST, SDKs, MCP and A2A use the same versioned credit objects and policy boundaries.
DETERMINISTIC AUTHORITY
Models can recommend. Approved policy authorizes.
Every Offer, Authorization, Obligation, settlement event and correction remains traceable.
- 01AssessModels may prepare a recommendation.
- 02AuthorizeApproved policy decides.
- 03RecordReceipts and Evidence preserve the outcome.
BORROW. BUILD. PROVE.
Turn performance into your next capital opportunity.
Accepted terms become clear obligations. Completed use and repayment become verified history.
Availability varies by jurisdiction, capital provider and product configuration.Verifiable Credit Infrastructure
Verifiable Credit Infrastructure for Humans and Agents
Identity, authority, capital, obligations, execution, repayment, and verified outcomes—coordinated through one shared credit kernel.
BORROW. BUILD. PROVE.
Private account, wallet, and credit data stay hidden until the exact Tenant workspace is verified. The hosted experience uses synthetic capital and grants no real-funds authority.
The Credit Loop
Borrow → Build → Repay → Prove
Turn each verified outcome into stronger, permissioned Credit State for the next capital decision.
Why IPO.ONE
Payments prove movement. Credit proves responsibility.
A payment can show that value moved. Credit must preserve who committed, under whose authority, on which terms, what became owed, what happened afterward, and whether that outcome can become reusable credit.
Payments ask Did value move? Credit must also ask Who is responsible—and what did they prove?
One kernel · two native entry modes
Different interfaces. One economic truth.
Human and Agent experiences converge on the same Offer, Obligation, Ledger, servicing, Evidence, and Credit State model.
- HumanConnect → Verify → Consent → Request → Offer → Accept → Repay → Build Credit
- AgentPrincipal → Agent Identity → Mandate → Request → Controlled Execution → Repay
- Capital ProviderReview authorized Evidence, author exact terms, and monitor verified outcomes.
- Developer / APIIntegrate through versioned API, SDK, MCP, and machine-readable receipts.
Evidence and Credit State
Transaction history is not credit history.
Credit State adds Obligation terms, payment timing, delinquency, cure, default, loss, resolution, authority provenance, and Evidence lineage. Credit Passport is a permissioned portable view—not a universal opaque score.
Capital Providers
Capital decision and protocol truth stay distinct.
Banks, fintech lenders, private credit, institutional Facilities, and compatible capital rails can author economic terms. IPO.ONE preserves permission, versioning, Ledger, servicing, reconciliation, and Evidence integrity.
Protocol architecture
Stable kernel. Replaceable adapters.
External rails can evolve without changing the canonical meaning of identity, authority, Offer, Obligation, repayment, or Evidence.
The responsibility layer
The Agent economy needs more than faster payments.
IPO.ONE turns identity, authority, obligations, execution, and repayment into verifiable Credit State—giving Humans and Agents a path from one successful outcome to the next source of capital.
BORROW. BUILD. PROVE.Portfolio command center
Your portfolio overview
Review your current credit position, next payment, and verified activity from one workspace.
Borrowing shortcuts
Start from the user you are serving
Human and Agent use different authority, then converge on the same Decision, Offer, Obligation, repayment, and Evidence record.
IPO.ONE products
Choose what you want to do
Each product keeps its own purpose while using the same identity, obligation, repayment, and Evidence record.
Workspace detailsIdentity, authority, and product status
Access modes
Human and Agent, one shared kernel
The interface and authority method change. Obligation, Ledger, risk, servicing, and Evidence do not fork.
Human Workspace
Application & Obligation
Consent, deterministic Offer, exact acceptance, repayment schedule, servicing, and owner Evidence remain one Human path.
- Offer
- Not requested
- Obligation
- Not created
- Servicing
- Not started
Agent Workspace
Identity & bounded authority
The Human Principal binds CAIP-10 identity and a scoped Mandate. The Agent receives machine-readable capability, never credentials or funds authority.
- Subject
- Not created
- Account proof
- Not submitted
- Mandate
- Not created
Verified activity
Recent credit activity
Base Sepolia · one exact market · test assets only
Secured Pool, read from server truth.
The same canonical Pool state supports Human liquidity and secured-credit positions. IPO.ONE verifies the approved deployment and reads a safe block; this page cannot sign or submit a transaction.
Independent truth axes
What IPO.ONE can verify right now
A deployed contract can remain true even when RPC, indexer, reconciliation, or a private AccountBinding is unavailable.
Public market · test USDC / WETH
Current read-only market
Base Sepolia exact Pool · waiting for server read
- Contract
- Unavailable
- Market ID
- Unavailable
- Safe block
- Unavailable
- Observed
- Unavailable
- Oracle
- Unavailable
- New-risk control
- Unavailable
Private position · Subject + AccountBinding required
My authorized Pool position
Public market data never grants access to a private position. IPO.ONE returns position values only for the authenticated Actor's owned Subject and active execution AccountBinding.
Read-only scenario review
Reviewing a hypothetical action only reports blockers and a preview. It creates no signature, allowance, RPC write, transaction, or funds movement.
- Reviewed scenario
- —
- Exact amount
- —
- Submission authority
- Unavailable · no transaction will be submitted
Refresh server truth first. An authoritative zero will be shown as zero; unavailable data will remain unavailable.
Human credit
Know every term. Own every step.
See your terms before you accept, follow one clear repayment plan, and verify every lifecycle event—all without real funds.
Your guided path
Start with a private sandbox profile
We will create an opaque profile and purpose-limited Consent. No name, bank login, wallet credential, or raw KYC is requested here.
- 1Get readyPrivate profile and Consent
- 2RequestAmount and schedule
- 3Review termsDecision and exact Offer
- 4ActivateSandbox Obligation
- 5Repay & verifySchedule and Evidence
ACCOUNT READINESS
Your sandbox identity
Create a profile and scoped Consent to prepare sandbox activation.
Your applications
Offers ready to review
Choose an application to review its current terms. Selection does not accept credit.
Product protectionsView protocol controls and safety boundaries Private protocol approved
Intent, Decision, Offer, exact acceptance, and shared Obligation use one approved private protocol. Capital, custody, disbursement, and production funds stay disabled.
Authenticated application
Request and price no-funds credit
Choose an amount and schedule. You will see an explainable Offer before anything is created.
- Lifecycle
- Created
- Servicing
- Current
- Days past due
- 0
- Schedule
- v1
- Outstanding
- $0.00
- Interest due
- $0.00
- Total repaid
- $0.00
Technical references
- Obligation ID
- —
- Sandbox rail receipt (offchain)
- Not executed
Early partial or full repayment is available after execution with no sandbox prepayment penalty. Fee → interest → principal; surplus is not posted.
M3 · public authenticated no-funds
Metered inference resource
Checking the exact hosted synthetic Provider profile. No external Provider or real funds are used.
- Provider / resource
- Not loaded
- Authorization cap
- Not loaded
- Consumed / remaining
- Load Evidence
- Current Obligation
- Not created
- Repayment
- Not available
- Usage Evidence
- Not loaded
Public-chain verification
Base Sepolia anchor
Not anchored. This sandbox Obligation and its repayments currently exist in IPO.ONE PostgreSQL only; no Base Sepolia transaction exists for this lifecycle.
- Server record
- Not loaded
- Evidence digest
- Not loaded
- Chain transaction
- Not submitted
- Chain finality
- Incomplete
- Indexer state
- Not observed
- Reconciliation
- Coverage pending
EVIDENCE-001B · owner only
Your durable Obligation timeline
Load the redacted PostgreSQL Evidence for this exact Obligation. Evidence digests are integrity checks, not blockchain transactions.
Developer detailsProtocol receipts and operation names
- 01Authority preflightpilotReadHumanSelfWaiting for server
- 02Credit IntentpilotRequestCreditWaiting for server
- 03Application readpilotReadCreditApplicationWaiting for server
- 04Decision & OfferpilotEvaluateCreditApplicationWaiting for server
- 05Exact acceptancepilotAcceptCreditOfferWaiting for server
- 06No-funds executionpilotExecuteSandboxObligationWaiting for server
PILOT-006 · public Beta feedback
Tell us where the product worked—or blocked you.
Choose structured signals only. This form has no comment box and accepts no name, contact detail, wallet address, KYC, or other PII.
Create or restore your Human Subject to submit one immutable categorical receipt.
PILOT-008A · cases & corrections
Flag a record without rewriting it.
Select one record already visible in your workspace and a closed reason. The original remains immutable; any correction is an additive Evidence event.
Create or restore your Human Subject, then select one current record.
Identity + authority
Human application boundary
Agent credit · Principal controlled
Same economics. Bounded machine authority.
A Human Principal must bind the Agent Subject and exact Consent-equivalent Mandate scope before the Agent application tools become available.
Activating a Mandate creates bounded authority; it does not create a Credit Intent, Offer, Obligation, execution, or repayment.
Authenticated machine journey
Intent → Decision → Offer → Acceptance → Execution
Server workflow receipts
Machine-verifiable handoff result
- Decision & Offer
- Returned only after Agent workflow
- Obligation lifecycle
- Returned only after active runtime workflow
Receipts return to the authenticated Agent runtime. They contain no credential, private key, reusable signature, or funds authority.
Dual-native parity
Different authority. One economic truth.
Private credit evidence
Checking serverDecision Passport sharing
This v1 artifact is a temporary, read-only view of the facts behind one current credit Decision—not a repayment-history Passport. You choose one authorized reviewer, how long access lasts, and exactly which facts are disclosed. Terminal repayment history appears separately in Credit Track Record.
Server-derived state
No Decision Passport loaded
Complete or restore an authenticated credit application. This view will not manufacture a score, Decision, or shareable proof.
Optional advanced sharing
Share the current Decision
Normal credit and Passport review need no internal identifier. Open this only when an invited same-Tenant reviewer has supplied its exact Actor reference.
Advanced: share with an exact invited reviewer
Complete a current Decision first. The verifier is never discovered or suggested by the browser.
Current sharing status
Shared Passport
Recover an existing Passport by technical ID
- Proof version
- —
- Issuer
- —
- Permitted use
- Private credit review
- Active period
- —
- Review access
- One bound same-Tenant reviewer
- Disclosed facts
- —
Issue or read an authorized artifact to inspect its selected, evidenced disclosures.
Technical receipt and integrity digests
- Source Decision Passport digest
- —
- Passport artifact digest
- —
These hashes verify integrity. They are not blockchain transaction hashes; public-chain status is shown separately in the Obligation Evidence receipt.
No artifact is trusted until an authenticated server read succeeds.
Verifier toolVerify a received proof online Not verified
Verification requires the exact authenticated verifier, current same-Tenant Membership, purpose, hash, version, source, and trusted server time.
Private proof lifecycle
Four authenticated operations create, read, verify, and terminally revoke a versioned artifact.
Evidence, not a score
Only selected factor grades, canonical reason codes, and exact Evidence lineage can be disclosed.
No bearer sharing
No public link, QR, download, credential, signature, cross-Tenant verifier, or production authority exists.
Principal-controlled Agent credit
Authorize once. Keep every limit visible.
A Human Principal approves identity and bounded authority before an Agent receives any application or runtime handoff.
Developer Agent integration
Versioned integration truth
One online Agent path. Thirteen protected operations.
Run the registered local reference Agent online or connect an external Agent through the protected HTTPS contract. Credentials remain server-side and every call is reauthorized.
One manifest. Fifteen local tools. No ambient authority.
Waiting for authenticated catalog and Principal state.
Principal-observable Agent lifecycle
Check authenticated Agent progress online
Create a verified Agent Subject and Draft Mandate first. The external Agent uses its own credential; this Principal browser reads only durable server truth.
What “use credit” means: the Agent executes one Mandate-approved purpose through the non-withdrawable sandbox rail. It cannot transfer the credit to an arbitrary wallet. The external Agent uses its own durable, revocable credential; the Principal browser can only check sanitized, persisted workflow receipts.
Developer API and workflow details
agent_mcp_registry.v2
Approved Agent API operations
Catalog presence is not authorization. The Host rechecks Subject, Mandate, admission and policy on every call. Approved local stdio MCP tools remain available as an optional developer transport.
Typed SDK compositions
Three staged workflows
Optional developer tooling
CLI reference runner
The CLI remains an optional integration and debugging tool. Normal product testing uses the online reference Agent above; external Agents call the protected HTTPS API with their own credential.
Versioned local contract
OpenAPI discovery
The document describes authentication requirements but contains no credential or production endpoint.
Exact unavailable capabilities
Not hidden. Not implied. Not enabled.
Capital provider workspace
Checking private gatewayCapital Partners
Review an exact borrower-authorized Passport, set transparent sandbox terms, and monitor the resulting Obligation from execution through repayment and Evidence.
Exact authorized application
Author sandbox terms
Technical authoring references
- Passport artifact
- —
- Credit Intent
- —
- Artifact proof
- —
Sign in through the invited Capital Partner workspace to restore borrower-authorized applications from server truth.
Canonical Offer receipt
Terms and authority
- Partner
- —
- Validity
- —
Technical Offer receipt
- Profile
- —
- Offer ID
- —
- Offer hash
- —
- Terms hash
- —
- Borrower
- —
Server-composed read model
Portfolio and Facility truth
Portfolio values come from canonical Offer, Obligation, servicing, repayment, and Evidence projections.
Explicit Phase 2 boundary
Bilateral terms are enabled; money movement is not
This workspace can review a bounded Passport, issue an exact synthetic Offer, and monitor canonical lifecycle truth. Public pools, deposits, custody, allocation, withdrawals, and real capital remain disabled.
Provider workspace · no funds
Checking serverProvider Network
Inspect one assigned sandbox intent from the authenticated Provider boundary. Exposure, delivery, and reconciliation remain server-derived, nonwithdrawable, and explicitly not deployed capital.
Exact assignment only
Load your assigned TransferIntent
Use the exact TransferIntent ID from your Provider assignment or invitation. This page cannot search for assignments; missing, expired, denied, and cross-Provider resources are not enumerated.
Current server state
No Provider intent loaded
The browser does not infer Provider exposure, facility state, earnings, or reconciliation from prototype data.
Mandate-bound assignment
Provider mandate
- Provider
- Server required
- Purpose
- Server required
- TransferIntent
- Server required
- Funding authority
- No · presentation only
Assigned no-funds exposure
Facility presentation
Asset unavailable until an exact intent is loaded.
Signed fixed-loopback delivery
Delivery & reconciliation
Acknowledgement is not funding, settlement, custody, or withdrawal authority. Exact retries reuse one idempotency key.
Historical example only · unapproved
Earnings simulation
Example rate: 1.25% of an exact loaded sandbox amount. It is nonbinding, unapproved, and cannot create Ledger, Evidence, or Provider entitlement.
Explicitly unavailable
Capital actions remain disabled
No TVL, public LP, remote Provider, mainnet, real capital, custody, or withdrawable balance is enabled.
Hyperliquid MVP · local no-funds
Checking contractTrading Capital
Hyperliquid testnet is the only MVP venue for this authenticated Facility and canonical Obligation. This local screen inspects and closes an existing synthetic Facility and lets the accountable Principal create or revoke the exact pre-signing Agent authorization. Facility creation, matching, funding simulation, and execution setup remain role-scoped API/SDK workflows. Other venue adapters remain disabled; no nonce, signature, redeemable settlement, external execution, or remote MCP is implied.
Exact bound resource only
Load one synthetic Facility
Use the Facility ID returned by an authorized Trading Capital API/SDK workflow. This page does not create or discover Facilities; denied, missing, and cross-Tenant resources remain non-enumerating.
Principal-controlled · pre-signing only
Agent Facility authorization
Load one exact Facility first. Creation and revocation require the authenticated Principal workspace; the Agent may only read the current authorization.
M2B-002 · read-only gate
Hyperliquid Testnet pre-write readiness
This is a queryable STOP receipt, not an execution control. Load the exact Facility and authorization to recover current server truth.
M2B-003 · dual-risk recovery
Pool health + Venue margin recovery
Load the exact Facility and authorization to recover current dual-risk STOP truth.
Overview
Server contract availability
Deterministic close path
Settle & prove
The settlement worker accepts no caller-supplied PnL, fee, cost, or price. It conserves synthetic contributions, creates no second Ledger, and cannot move production funds.
Authentication + bounded execution
Checking serverWallet & Permissions
IPO.ONE login identifies the Actor and workspace. A separate execution AccountBinding proves control of one external account; only canonical Mandate, CreditLine, Obligation, and risk state can derive bounded execution authority.
Current server session
Checking authentication
No wallet or server-session authority is assumed before verification.
Authentication remains separate
Existing OIDC/SIWE session, Tenant, Actor, Role, and recovery semantics are unchanged by execution account actions.
Human + Agent AccountBinding
One dual-native proof contract binds an execution account to an existing Subject and grants zero authority by itself.
Exact resolver & Evidence
Gateway-owned atomic persistence records reservation, prepared execution, simulation, preflight, Events, Evidence, and outbox without moving funds.
Owned obligations
Every position, reconciled to server truth.
Review bounded owned references, exact current state, schedule, authority, sandbox rail, and immutable Evidence.
Selected shared position
Obligation status
Refresh exact owner-authorized server state before relying on an amount or status.
Bounded owned-resource composition
My obligations
Sign in to recover bounded Actor-owned Obligation references.
Positions
Unrefreshed or denied references reveal no financial values.
Select a current position
Refresh server state, then select one exact Obligation. Browser state is never financial truth.
Shared obligation.v2
Current position
Technical references
- Obligation
- —
- Execution receipt
- —
- State version
- —
Metered inference resource
- Provider / resource
- Not loaded
- Authorization cap
- Not loaded
- Consumed / remaining
- Load Evidence
- Latest usage Evidence
- Not loaded
No external Provider or real funds are enabled.
Payment plan
Version history & corrections
Load Evidence to verify immutable state changes.
Read boundary
One state machine, exact owner reads
Human Consent and Agent Mandate change entry presentation only. List references come from the bounded authenticated workspace and every value is reauthorized by exact Obligation ID.
Human repayment
Repay with the schedule in view.
Post synthetic repayment against the exact shared Obligation and inspect deterministic allocation.
Shared servicing kernel
Servicing Case
Authenticated server truth
My positions
Refresh to load current balances and trusted-time servicing state for these authorized references.
Only Actor-bound opaque references are shown. Select one position to load its exact authorized state.
Accept and execute one exact sandbox Obligation to open its servicing view.
Case stage
DPD is derived by the authenticated worker; this page cannot change time or classification.
Cure or repay
Execute the sandbox Obligation before posting a repayment.
- Past-due principal
- $0.00
- Past-due interest
- $0.00
- Past-due fees
- $0.00
Fee → interest → principal. Cure is confirmed only by the returned Obligation.
Payment plan
Provider sandbox
Signed Provider boundary verified
One fixed loopback Provider can receive an exact assigned intent, acknowledge it, and return a signed callback without duplicating canonical state.
Capability status only — this Obligation has no Provider execution. Loopback, synthetic, no-funds, nonwithdrawable; public or remote Provider access remains disabled.
Owner Evidence
Verify the lifecycle, not a screenshot.
Load redacted immutable events for the exact Obligation owned by this authenticated Human session.
Shared immutable timeline
Obligation Evidence
Session projection only. Durable Evidence is loaded through the already-approved owner or Agent Evidence operation; this page creates no new read permission.
EVIDENCE-001C · Base Sepolia
Checking operationPublic Registry Evidence
Verify one finalized, redacted testnet credit-registry lifecycle without treating it as the signed-in user’s own repayment record.
Enter one exact public authorization hash. The authenticated Gateway returns only the bounded synthetic Base Sepolia observation.
——Obligation Evidence
Inspect the durable server lifecycle behind one shared Human or Agent Obligation.
EVIDENCE-001A
Durable audit timeline
Enter an exact Obligation ID. Access is verified by the private Gateway.
Evidence-derived only
Checking serverCredit Track Record
Read the durable Credit State rebuilt from finalized terminal Credit Outcomes. Browser history is not credit truth, and this qualitative record cannot authorize funds or change a limit automatically.
Current record
No verified lifecycle loaded
Restore an owned Subject and load its outcome-derived Credit State. No positive history is inferred from an empty browser state.
Finalized outcomes only
Durable Credit State
- Decision Passport
- Not loaded
- Completed cycles
- 0
- Latest terminal outcome
- Not loaded
- Repayment reliability
- Not loaded
- Total loss
- $0.00
Outcome-derived record
Only finalized on-time, late or modified, and written-off Credit Outcomes can update this state.
Qualitative factors
No universal score, wallet-history inference, funds authority, or automatic limit change is created.
Generated report
Create a bounded JSON or formula-safe CSV artifact from the exact owned Obligation and its persisted Evidence.
Server-generated artifacts
Checking serverReports & Exports
Create, inspect, retrieve, and revoke a bounded report derived from the current owned Obligation and its persisted Evidence. The browser transports exact verified bytes; it does not author official content.
Current artifact
No official report loaded
Load an owned Obligation first. Report content is generated and hashed by the server from bounded, redacted Evidence.
Authenticated command
Create official activity report
The server reauthorizes the exact owned Obligation and limits the source to 50 redacted Evidence events.
Authorization rechecked
Read or retrieve exact artifact
Every read and retrieval revalidates active same-Tenant ownership. Expired or revoked artifacts are unavailable.
Server metadata only
Artifact integrity
- Content SHA-256
- —
- Artifact hash
- —
- Evidence source
- —
- Expires
- —
- Authorization
- Rechecked on access
- Production fee policy
- Unavailable · principal and unrealized PnL excluded as fee bases
No HTML export, public link, bearer grant, PII, secret, raw transaction, signed URL, production fee calculation, mainnet authority, or real-funds authority is created.
Permissioned control plane · WEB-008
Portfolio risk, with protective action.
Read one exact tenant portfolio and freeze one exact Agent Subject through the authenticated Gateway. Every result is policy-bound and PII-free.
Protected workspace
Verify your presence
Use a Passkey to access this role’s protected operations.
Servicing governance · Local sandbox
Review an exact action
Propose, review and execute are separate recorded actions. The proposer cannot approve their own request.
Verify your presence, then load the current server records.
Plan schedule and verification references
Protective review
Active Agent directory
Read a bounded list of synthetic Agents, then select one for the existing protective freeze control.
M2 Pool control view · aggregate only
Solvency, oracle, reconciliation
No account address, raw transaction, signer, or liquidation submission is exposed.
Load the exact authorized Tenant risk portfolio first.
Aggregate exposure
Tenant portfolio posture
Restoring the authorized Tenant portfolio from server truth.
Technical details
- Portfolio reference
- Not recovered
- Queue reference
- Not recovered
Identity posture
Capacity posture
Servicing posture
Asset exposure
PII-free portfolio view
PILOT-005 · privacy-safe product truth
Public Beta lifecycle health
Aggregate Human and Agent progress from durable protocol facts—without trackers, raw identifiers, KYC, or borrower PII.
Load the Tenant portfolio to verify the product funnel.
PILOT-006 · privacy-safe feedback truth
Public Beta experience
Aggregate categorical signals from Human and Agent entry modes. No feedback, Subject, Actor, wallet, KYC, or Event identifier is returned.
Load the Tenant portfolio to aggregate feedback.
PILOT-008A · remediation queue
Cases & additive corrections
Review closed-category Human and Agent cases. Assigning, upholding, and correcting are explicit actions; none changes balances, limits, or the original record.
Risk, Operations, or Auditor access with recent MFA is required to read this queue.
REQ-PILOT-002 · Public Beta readiness
Public no-funds Beta operating readiness
The Founder activation decision is already approved. This read-only view tracks exact release, authentication, recovery, reconciliation, abuse-control, and Beta-notice verification without granting another activation authority.
Risk, Operations, or Auditor access with recent MFA is required. This view verifies delivery state and cannot change the approved launch policy.
SERVICING-002B · private work queue
Adverse Obligation review
Trusted-time delinquency and default cases, ordered by severity. This surface is read-only and contains no borrower PII.
Risk or Operations access and recent phishing-resistant MFA are verified on every read.
Read-only · PII excluded · no disposition authority · synthetic obligations only · no real funds.
V9-008 · checked-in control evidence
Operational assurance, without invented runtime state
Policy and runbook facts are separated from live Tenant reads. A checked-in control never becomes a current alert, reconciliation result, incident, or approval merely because it is rendered here.
No operator alert read has been verified.
Policy evidence onlyNo current reconciliation run has been loaded.
Worker evidence onlyNo incident acknowledgement or resolution authority is exposed.
Runbook baseline onlyA proposal locator is never approval authority.
Exact command requiredProtective-only command
Freeze Agent Subject
Suspends one exact pending or active Agent Subject. This surface cannot unfreeze, increase limits, move funds, or expand authority.
Select an authorized queue case for protective review. Selecting a case does not freeze it.
Risk or Operations authority is verified only when the command is submitted.
Explicitly unavailable
Closed permissions by design
Agent integration
From approval to action. No hidden authority.
Use one Principal-approved handoff with the approved local Agent Host. Credentials and real funds never travel in the packet.
Your integration path
Authorize this Agent
A Human Principal creates the Agent Subject and sets exact sandbox limits before any machine workflow is available.
- 1AuthorizePrincipal + bounded Mandate
- 2Prove identityOne-use CAIP-10 proof
- 3Request termsCredential-free handoff
- 4Run & verifyObligation, repayment, Evidence
Checked-in catalog + runtime response
V9 capability contract
- Catalog maturity
- Checking
- Enabled transports
- Checking
- V9 destinations
- 0/13 verified
- Safety
- Real funds disabled
No diagram, prototype export, marketing label, or browser counter can add a capability absent from the authenticated catalog.
Machine-readable integrationView handoff packet, 15 Agent operations, OpenAPI, and request log Waiting for authority
Non-authorizing manifest
Principal → Agent capability packet
This non-authorizing packet advertises thirteen local Agent operations and three staged workflows. The loopback OpenAPI describes the server boundary; credentials and funds authority never enter the packet.
Local Agent MCP
Approved Host operations
Local no-funds Agent client
Reference Agent runner
Agent API contract
Approved authenticated workflows
Authenticated request telemetry