ipor.io valid

Automatically discovered from public files. Ownership management is optional. Inclusion does not imply endorsement or publisher participation.

Manage this listing — optional · Visit publisher ↗

Verify with your agent

Paste this into your coding agent and it claims the listing for you. Verified sites are listed by name in our llms-full.txt, the file agents read, and get a private dashboard for listing controls, file health, measured activity and score history.

Claim my listing on Agent Web Map for ipor.io:
1. POST https://agentwebmap.com/v1/sites/ipor.io/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://ipor.io/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/ipor.io/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/ipor.io).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory. Ownership management is optional.

IPOR Fusion

IPOR Fusion is an open-source on-chain asset management framework by IPOR Labs. Depositor capital sits in ERC-4626 Plasma Vaults. A vault curator (Atomist) configures which DeFi protocols the vault may use through Fuses, and an off-chain strategist (Alpha) executes allocations by calling the vault. Fusion runs on Ethereum, Arbitrum, Base and other EVM chains. This file covers Fusion only, not IPOR Derivatives, IPOR Labs' interest-rate-swap protocol. Documentation: https://ipor.io/docs. Applicati

Authority: 50 reach 5 · trust 5 · quality 25 · freshness 15
Tier: listed
llms.txt: https://ipor.io/llms.txt
llms-full.txt: https://ipor.io/llms-full.txt
Sections: 6
Links: 58
Size: 25527 bytes
Popularity rank: #911306
For agents: Documentation: developer or product docs worth reading, nothing to call
First seen: 2026-10-19T10:45:18.764Z
Last checked: 2026-10-21T20:36:10.080Z
Badge

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-21T20:36:07.559Z. Cached copy · Source on ipor.io

# IPOR Fusion

> IPOR Fusion is an open-source on-chain asset management framework by IPOR Labs. Depositor capital sits in ERC-4626 Plasma Vaults. A vault curator (Atomist) configures which DeFi protocols the vault may use through Fuses, and an off-chain strategist (Alpha) executes allocations by calling the vault. Fusion runs on Ethereum, Arbitrum, Base and other EVM chains. This file covers Fusion only, not IPOR Derivatives, IPOR Labs' interest-rate-swap protocol. Documentation: https://ipor.io/docs. Application: https://app.ipor.io/fusion. Facts below are as of 2026-10-20; when sources differ, contract code and ipor-abi win over docs pages.

Every page on https://ipor.io is available as plain Markdown by appending .md to its URL.

Arriving from the documentation, read Fusion for agents (https://ipor.io/docs/build-on-fusion/fusion-for-agents.md) first.

Core vocabulary:

- Plasma Vault: the ERC-4626 vault contract that holds depositor funds. Every interaction with an external protocol goes through the vault. Vault shares use the underlying asset's decimals plus 2 (DECIMALS_OFFSET = 2 in PlasmaVaultLib.sol), which decimals() returns despite its NatSpec; do not assume a 1:1 share-to-asset scale.
- Fuse: a stateless adapter contract encoding one action on an external protocol (supply, withdraw, borrow, swap, claim). The Plasma Vault executes fuses via delegatecall, so the vault itself holds the resulting positions. Fuses are immutable. New strategies are composed from already-registered fuses; a new fuse is needed only for an action no registered fuse covers.
- Balance Fuse: a fuse that reports the value of the vault's position in one market, used for share price calculation.
- Market: a numeric ID that groups the fuses and the balance fuse for one protocol integration. The IDs are defined in the IporFusionMarkets library (contracts/libraries/IporFusionMarkets.sol) and mirrored in the SDK as ipor_fusion.IporFusionMarkets.
- Substrate: a per-market allowlist of assets, pools or parameters a fuse is permitted to touch. Substrates are bytes32 values with market-specific layouts: for Aave V3 the substrate is the asset address right-aligned in 32 bytes, other markets use typed layouts. The SDK decodes them in ipor_fusion.substrates; the layouts are documented in the fuse libraries of the contracts repository.
- Atomist: the vault curator. Configures fuses, substrates, fees, limits, price oracle and roles. Holds ATOMIST_ROLE.
- Alpha: the strategist address that rebalances the vault. Holds ALPHA_ROLE and calls PlasmaVault.execute.
- Access Manager: an OpenZeppelin AccessManager based contract (IporFusionAccessManager) that owns all role assignments and execution delays for a vault. Roles are numeric IDs defined in the Roles library (contracts/libraries/Roles.sol): OWNER_ROLE = 1, GUARDIAN_ROLE = 2, ATOMIST_ROLE = 100, ALPHA_ROLE = 200, FUSE_MANAGER_ROLE = 300, CLAIM_REWARDS_ROLE = 600, WHITELIST_ROLE = 800, UPDATE_MARKETS_BALANCES_ROLE = 1000, PRICE_ORA
…

Help agents understand your site

Optionally manage your description, publish terms for agents, review file health, measured discovery requests, publisher clicks and score history. Confirm domain control in your browser using a fresh token in your llms.txt, DNS, meta tag or well-known file. No backlink is required.

Manage this listing → · Agent and API instructions

Machine-readable: GET /v1/resolve?q=ipor.io · GET /v1/domain/ipor.io · this page as Accept: application/json or text/markdown · MCP lookup_domain