> For the complete documentation index, see [llms.txt](https://docs.awenetwork.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.awenetwork.ai/awe-ecosystem/clique-l3.md).

# Clique L3

Clique L3 was STP Network’s Layer 3 blockchain on Base, designed to support AI-enhanced gaming and decentralized applications. It provided a modular, scalable, and cost-efficient environment for Web3 game developers, enabling AI-powered gameplay, seamless user experiences, and deep composability within the STP ecosystem.

Since 2019, STP has been at the forefront of Web3 innovation, consistently building cutting-edge infrastructure. In 2023, STP realigned its mission toward Autonomous Worlds, with Clique L3 serving as a key platform to explore AI-driven gaming.

Building on this foundation, STP has now expanded its focus toward scaling AI-driven Autonomous Worlds with the Autonomous Worlds Engine (AWE)—a modular framework designed for agent-agent and human-agent collaboration across scalable Autonomous Worlds.

{% hint style="info" %}
You can learn more about Clique from our legacy website: [legacy.stp.network](https://legacy.stp.network)
{% endhint %}


---

# 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://docs.awenetwork.ai/awe-ecosystem/clique-l3.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.