> For the complete documentation index, see [llms.txt](https://docs-v4.venus.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs-v4.venus.io/technical-reference/reference-isolated-pools/pool-registry/pool-registry-interface.md).

# PoolRegistryInterface

The current [`PoolRegistryInterface`](https://github.com/VenusProtocol/isolated-pools/blob/v4.4.0/contracts/Pool/PoolRegistryInterface.sol) defines two return structures and five read functions.

## Structures

```solidity
struct VenusPool {
    string name;
    address creator;
    address comptroller;
    uint256 blockPosted;
    uint256 timestampPosted;
}

struct VenusPoolMetaData {
    string category;
    string logoURL;
    string description;
}
```

`comptroller` is the pool's Comptroller **proxy**, not an implementation address. `creator`, `blockPosted`, and `timestampPosted` describe registration; they do not prove that the pool is currently promoted or that every market is listed.

## Read API

```solidity
function getAllPools() external view returns (VenusPool[] memory);

function getPoolByComptroller(
    address comptroller
) external view returns (VenusPool memory);

function getVTokenForAsset(
    address comptroller,
    address asset
) external view returns (address);

function getPoolsSupportedByAsset(
    address asset
) external view returns (address[] memory);

function getVenusPoolMetadata(
    address comptroller
) external view returns (VenusPoolMetaData memory);
```

The registry has no active/deprecated flag and does not remove exit or debt obligations. Consumers must combine these results with Comptroller listing and pause state, VToken balances and debt, and the documented product lifecycle.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs-v4.venus.io/technical-reference/reference-isolated-pools/pool-registry/pool-registry-interface.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.