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

# Genius Architecture Overview

The Genius Protocol is split into 7 different repositories each containing a specified functionality. For this stage of the documentation, the end stage is detailed in each of the following places and the current stage of implementation is noted with relevant code snippets.

## Genius EVM Smart Contracts

{% embed url="<https://shuttlelabs.notion.site/Genius-Smart-Contracts-7819eb041d864d0e857a70c0faef2cbf>" %}

## Genius DB

Standard Postgres DB. Will need secondary audit once we start doing state based orders and holding encrypted data. As of right now holds non-vital user information e.g txn history etc and auth is done through Lit Protocol.

## Genius Executor

The Genius Executor is responsible for interacting with the Lit Protocol. It serves a variety of function e.g minting a capacity credit, executing swaps, etc. The reason that the executor is split from the client is so that we can integrate state based orders in the future without bogging down the frontend service.

{% embed url="<https://www.loom.com/share/cc13c3b20ac24b22b77db077c830f127>" %}

## Genius Memecoin

Genius API TEST

```c
// genius-test.js
// node genius-gauss-test.js

const GENIUS_API_URL = "https://api.tradegenius.com/v1/token-launch/test";

const GENIUS_API_KEY = process.env.GENIUS_API_KEY || "";

const WALLET_ADDRESS = "0x89d63044e387414d3de026a8d08afefd819ea873";

const payload = {
  action: "launch_token",
  mode: "test",
  walletAddress: WALLET_ADDRESS,

  token: {
    name: "crow",
    symbol: "CROW",
    decimals: 18,
    totalSupply: "1000000000",
    network: "BNB Chain",
  },

  request: "Launch a CROW token through Genius Terminal.",
  description:
    "Gauss is an experimental community token inspired by intelligence, mathematics and the Genius ecosystem.",

  dryRun: true,
};

async function testGeniusAPI() {
  console.log("Genius API test request:");
  console.log(JSON.stringify(payload, null, 2));

  if (!GENIUS_API_KEY) {
    console.log("\n GENIUS_API_KEY is Null");
    return;
  }

  const response = await fetch(GENIUS_API_URL, {
    method: "POST",
    headers: {
      "Content-Type": "application/json",
      Authorization: `Bearer ${GENIUS_API_KEY}`,
    },
    body: JSON.stringify(payload),
  });

  const responseText = await response.text();

  console.log("\nHTTP Status:", response.status);
  console.log("Response:", responseText);

  if (!response.ok) {
    throw new Error(`Genius API request failed: ${response.status}`);
  }
}

testGeniusAPI().catch((error) => {
  console.error("Error:", error.message);
  process.exitCode = 1;
});
```

## Genius Github Docs

About Mintlify Starter Kit

{% embed url="<https://github.com/Shuttle-Labs/genius-docs>" %}

## Genius Quoting Engine

The Quoting Engine is responsible for providing quotes with calldata for user swaps as well as user staking actions.

{% embed url="<https://www.loom.com/share/16efa8fe02e84bd7a218b66d4612da38>" %}


---

# 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://geniusterminal.gitbook.io/genius-docs/genius-architecture-overview.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.