Verifiable Credit Infrastructure
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
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
Human and Agent experiences converge on the same Offer, Obligation, Ledger, servicing, Evidence, and Credit State model.
Evidence and Credit State
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
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
External rails can evolve without changing the canonical meaning of identity, authority, Offer, Obligation, repayment, or Evidence.
The responsibility layer
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
Review your current credit position, next payment, and verified activity from one workspace.
Borrowing shortcuts
Human and Agent use different authority, then converge on the same Decision, Offer, Obligation, repayment, and Evidence record.
IPO.ONE products
Each product keeps its own purpose while using the same identity, obligation, repayment, and Evidence record.
Access modes
The interface and authority method change. Obligation, Ledger, risk, servicing, and Evidence do not fork.
Human Workspace
Consent, deterministic Offer, exact acceptance, repayment schedule, servicing, and owner Evidence remain one Human path.
Agent Workspace
The Human Principal binds CAIP-10 identity and a scoped Mandate. The Agent receives machine-readable capability, never credentials or funds authority.
Verified activity
Human credit
See your terms before you accept, follow one clear repayment plan, and verify every lifecycle event—all without real funds.
Your guided path
We will create an opaque profile and purpose-limited Consent. No name, bank login, wallet credential, or raw KYC is requested here.
Intent, Decision, Offer, exact acceptance, and shared Obligation use one approved private protocol. Capital, custody, disbursement, and production funds stay disabled.
Authenticated application
Choose an amount and schedule. You will see an explainable Offer before anything is created.
Early partial or full repayment is available after execution with no sandbox prepayment penalty. Fee → interest → principal; surplus is not posted.
Public-chain verification
Not anchored. This sandbox Obligation and its repayments currently exist in IPO.ONE PostgreSQL only; no Base Sepolia transaction exists for this lifecycle.
EVIDENCE-001B · owner only
Load the redacted PostgreSQL Evidence for this exact Obligation. Evidence digests are integrity checks, not blockchain transactions.
PILOT-006 · design-partner feedback
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.
Identity + authority
Agent credit · Principal controlled
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
Server workflow receipts
Receipts return to the authenticated Agent runtime. They contain no credential, private key, reusable signature, or funds authority.
Dual-native parity
Private credit evidence
Checking serverThis 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
Complete or restore an authenticated credit application. This view will not manufacture a score, Decision, or shareable proof.
Optional advanced sharing
Normal credit and Passport review need no internal identifier. Open this only when an invited same-Tenant reviewer has supplied its exact Actor reference.
Complete a current Decision first. The verifier is never discovered or suggested by the browser.
Current sharing status
Issue or read an authorized artifact to inspect its selected, evidenced disclosures.
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.
Verification requires the exact authenticated verifier, current same-Tenant Membership, purpose, hash, version, source, and trusted server time.
Four authenticated operations create, read, verify, and terminally revoke a versioned artifact.
Only selected factor grades, canonical reason codes, and exact Evidence lineage can be disclosed.
No public link, QR, download, credential, signature, cross-Tenant verifier, or production authority exists.
Principal-controlled Agent credit
A Human Principal approves identity and bounded authority before an Agent receives any application or runtime handoff.
Versioned integration truth
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. Thirteen local tools. No ambient authority.
Waiting for authenticated catalog and Principal state.
Principal-observable Agent lifecycle
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.
agent_mcp_registry.v2
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
Optional developer tooling
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
The document describes authentication requirements but contains no credential or production endpoint.
Exact unavailable capabilities
Capital provider workspace
Checking private gatewayReview an exact borrower-authorized Passport, set transparent sandbox terms, and monitor the resulting Obligation from execution through repayment and Evidence.
Exact authorized application
Sign in through the invited Capital Partner workspace to restore borrower-authorized applications from server truth.
Canonical Offer receipt
Server-composed read model
Portfolio values come from canonical Offer, Obligation, servicing, repayment, and Evidence projections.
Explicit Phase 2 boundary
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 serverInspect 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
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
The browser does not infer Provider exposure, facility state, earnings, or reconciliation from prototype data.
Mandate-bound assignment
Assigned no-funds exposure
Asset unavailable until an exact intent is loaded.
Signed fixed-loopback delivery
Acknowledgement is not funding, settlement, custody, or withdrawal authority. Exact retries reuse one idempotency key.
Historical example only · unapproved
Example rate: 1.25% of an exact loaded sandbox amount. It is nonbinding, unapproved, and cannot create Ledger, Evidence, or Provider entitlement.
Explicitly unavailable
No TVL, public LP, remote Provider, mainnet, real capital, custody, or withdrawable balance is enabled.
Hyperliquid MVP · local no-funds
Checking contractHyperliquid testnet is the only MVP venue for this authenticated Facility and canonical Obligation. This local screen inspects and closes an existing synthetic Facility; creation, matching, funding simulation, and execution setup are role-scoped API/SDK workflows. Other venue adapters remain disabled; no redeemable settlement, external execution, or remote MCP is implied.
Exact bound resource only
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.
Overview
Deterministic close path
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 serverIPO.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
No wallet or server-session authority is assumed before verification.
Existing OIDC/SIWE session, Tenant, Actor, Role, and recovery semantics are unchanged by execution account actions.
One dual-native proof contract binds an execution account to an existing Subject and grants zero authority by itself.
Gateway-owned atomic persistence records reservation, prepared execution, simulation, preflight, Events, Evidence, and outbox without moving funds.
Owned obligations
Review bounded owned references, exact current state, schedule, authority, sandbox rail, and immutable Evidence.
Selected shared position
Refresh exact owner-authorized server state before relying on an amount or status.
Bounded owned-resource composition
Sign in to recover bounded Actor-owned Obligation references.
Unrefreshed or denied references reveal no financial values.
Refresh server state, then select one exact Obligation. Browser state is never financial truth.
Shared obligation.v2
Load Evidence to verify immutable state changes.
Read boundary
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
Post synthetic repayment against the exact shared Obligation and inspect deterministic allocation.
Shared servicing kernel
Authenticated server truth
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.
DPD is derived by the authenticated worker; this page cannot change time or classification.
Execute the sandbox Obligation before posting a repayment.
Fee → interest → principal. Cure is confirmed only by the returned Obligation.
Provider sandbox
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
Load redacted immutable events for the exact Obligation owned by this authenticated Human session.
Shared immutable timeline
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 operationVerify 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.
——Inspect the durable server lifecycle behind one shared Human or Agent Obligation.
EVIDENCE-001A
Enter an exact Obligation ID. Access is verified by the private Gateway.
Evidence-derived only
Checking serverRead 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
Restore an owned Subject and load its outcome-derived Credit State. No positive history is inferred from an empty browser state.
Finalized outcomes only
Only finalized on-time, late or modified, and written-off Credit Outcomes can update this state.
No universal score, wallet-history inference, funds authority, or automatic limit change is created.
Create a bounded JSON or formula-safe CSV artifact from the exact owned Obligation and its persisted Evidence.
Server-generated artifacts
Checking serverCreate, 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
Load an owned Obligation first. Report content is generated and hashed by the server from bounded, redacted Evidence.
Authenticated command
The server reauthorizes the exact owned Obligation and limits the source to 50 redacted Evidence events.
Authorization rechecked
Every read and retrieval revalidates active same-Tenant ownership. Expired or revoked artifacts are unavailable.
Server metadata only
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
Read one exact tenant portfolio and freeze one exact Agent Subject through the authenticated Gateway. Every result is policy-bound and PII-free.
Aggregate exposure
Restoring the authorized Tenant portfolio from server truth.
Asset exposure
PILOT-005 · privacy-safe product truth
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
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.
SERVICING-002B · private work queue
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
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
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
Agent integration
Use one Principal-approved handoff with the approved local Agent Host. Credentials and real funds never travel in the packet.
Your integration path
A Human Principal creates the Agent Subject and sets exact sandbox limits before any machine workflow is available.
Checked-in catalog + runtime response
No diagram, prototype export, marketing label, or browser counter can add a capability absent from the authenticated catalog.
Non-authorizing manifest
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
Local no-funds Agent client
Agent API contract
Authenticated request telemetry
Access IPO.ONE
Choose a familiar account, then connect one approved test network. Identity proves who you are; Principal and Mandate rules still decide what you can do.
Authenticated session
Your secure host-only session has been verified. Product permissions remain controlled by your server-side role, Consent, and Mandate.
One verified Human identity may be enrolled in more than one role. This session receives only the role selected here.
One secure session across the Human and Agent workspaces.
Checking available sign-in methods…
Check the server again or share a privacy-safe diagnostic through your original invitation channel.
Protected actions remain blocked. Retry the same server-bound invalidation before starting a fresh wallet sign-in.
Copy a privacy-safe diagnostic and send it through your original IPO.ONE invitation channel. It excludes cookies, wallet addresses, tokens, and private resource IDs.
authentication_unavailableunavailableDiscovering browser wallets…
Wallet names and icons are untrusted display metadata. Selection stays in memory and never requests an account, network, or signature by itself. Account, network, Provider, or disconnect changes invalidate the previous host session before protected work can continue.
Authentication is not credit authority. A wallet address or Google account cannot create a Mandate, approve an Offer, or move funds.
Both test networks use the same chain-agnostic Obligation kernel.
Your wallet will ask for account access and, if needed, permission to add or switch the selected test network.
Explicit action confirmation
Review the exact no-funds action before IPO.ONE submits it to the authenticated server.
This confirmation does not create a blockchain transaction. A BaseScan link appears only after a separately verified Base Sepolia anchor transaction exists.
Nothing has been submitted.