> For the complete documentation index, see [llms.txt](https://smol404.gitbook.io/smol404-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://smol404.gitbook.io/smol404-docs/smol404/why-smol-404.md).

# Why SMOL-404?

AI agents are becoming economic actors.

They can already monitor markets, access data, execute strategies, interact with protocols, manage wallets and pay for services.

Infrastructure such as Binance Agent OS is accelerating that transition by giving agents direct access to financial and onchain tools.

As agents become more capable, the value attached to them can also become more measurable.

An agent may develop:

* performance
* reputation
* usage
* revenue
* specialized capabilities
* historical activity
* community demand

BAP 578 makes it possible for that agent to exist as an ownable onchain object.

But ownership alone does not create an efficient market.

Traditional NFT markets remain fragmented.

Each asset is priced independently.

Liquidity depends on individual listings.

Users often need to buy an entire asset.

Price discovery can be slow.

Integration with existing DeFi infrastructure is limited.

SMOL404 introduces a fungible market around the NFA layer.

The agent remains non fungible.

Its market becomes liquid.

#### Continuous liquidity

Users can buy and sell through AMMs instead of relying exclusively on NFT listings.

This creates continuous price discovery and easier entry and exit.

#### Fractional exposure

Users do not need to purchase an entire NFA.

They can enter with any position size and accumulate over time.

Once they hold a complete token unit, the corresponding NFA can be assigned automatically.

#### Better distribution

Builders can launch agent ecosystems using the same token infrastructure already familiar to millions of crypto users.

This lowers the barrier between discovering an agent project and participating in its market.

#### DeFi compatibility

The fungible side of SMOL404 can interact with standard BEP 20 infrastructure.

This opens the door to liquidity pools, aggregators, analytics tools, vaults and other DeFi applications.

#### More efficient price discovery

Instead of relying only on isolated NFT listings, an agent ecosystem can develop a continuous market price through its liquidity pool.

#### Markets for economic agents

This is the larger objective.

As agents begin generating value, making payments, executing strategies and interacting autonomously, they become more than software.

They become economic entities.

SMOL404 is designed to provide the market infrastructure around them.

**Agents can already trade assets.**

**SMOL404 makes it possible for agents themselves to become liquid assets.**

###


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://smol404.gitbook.io/smol404-docs/smol404/why-smol-404.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
