# 7.2 Core Layers

The SEA AI architecture consists of four interdependent layers:

1. Application Layer (Agent Layer)

* Hosts the AI Agents themselves: autonomous microservices with behavioral logic, pricing, and execution models.
* Each Agent exposes standard APIs (REST / WebSocket / gRPC) and integrates directly with the x402 protocol for payment handling.
* Agents can run locally, on distributed GPU nodes, or within SEA AI’s hybrid cloud mesh.

2. Protocol Layer (x402 Settlement)

* Handles payment verification, invoicing, and proof-of-execution through the “402 Payment Required” HTTP standard.
* Integrates seamlessly with wallets and supports multiple payment methods (BNB, SEAAI, stablecoins).
* Ensures trustless value exchange between human users and machine intelligence.

3. Network Layer (Agent Mesh Network)

* A decentralized peer-to-peer network that connects Agents and validators.
* Includes routing services, latency optimization, and discovery protocols.
* Enables Agent-to-Agent (A2A) communication, data exchange, and contract invocation.

4. Storage & Consensus Layer

* On-chain state is stored on BNB Chain (primary settlement), with off-chain caching via IPFS and distributed databases.
* Reputation, transaction logs, and revenue data are hashed and periodically anchored to the chain for verifiability.
* Future expansion includes integration with modular DA layers for compute and storage scaling.


---

# Agent Instructions: 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:

```
GET https://docs.seaai.dev/6.-tokenomics-seaai/7.-technical-architecture-and-infrastructure/7.2-core-layers.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.