> 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/intro/what-is-bap-578.md).

# What is BAP-578?

BAP 578 is a BNB Chain application standard built around Non Fungible Agents, or NFAs.

An NFA is an onchain representation of an AI agent.

Unlike a traditional NFT, an NFA can represent a persistent digital entity with its own identity, metadata, state, provenance and evolving activity.

This matters because the agent economy is moving beyond simple chatbots.

With infrastructure such as Binance Agent OS, agents can increasingly access market data, interact with APIs, use specialized Skills, operate wallets, make payments and execute transactions onchain.

BAP 578 gives these agents something equally important: a persistent identity that can exist, evolve and be owned onchain.

The distinction is simple:

**Agent OS defines what an agent can do.**

**BAP 578 defines which agent is doing it.**

Together, they create the foundations for persistent onchain economic agents.

###


---

# 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/intro/what-is-bap-578.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.