Merge pull request #58 from aptos-labs/rename-build-to-geomi

feat: rename Aptos Build to Geomi

Author: 0xmaayan

README.md

@@ -3,13 +3,13 @@
 ## Prerequisite
 
 - [node and npm](https://nodejs.org/en) (npm ≥ 5.2.0)
-- Build Bot Api Key
+- Geomi Bot Api Key
 
-### Generate a `Build Bot Api Key`
+### Generate a `Geomi Bot Api Key`
 
-To be able to make [Aptos Build](https://build.aptoslabs.com/) actions like managing api keys, etc. Follow those instruction to generate a new Bot Api Key to use with the MCP
+To be able to make [Geomi](https://geomi.dev/) actions like managing api keys, etc. Follow those instruction to generate a new Bot Api Key to use with the MCP
 
-1. Go to [https://build.aptoslabs.com/](https://build.aptoslabs.com/)
+1. Go to [https://geomi.dev/](https://geomi.dev/)
 2. Click on your name in the bottom left corner
 3. Click on "Bot Keys"
 4. Click on the "Create Bot Key" button

integration_guides/claude_code.md

@@ -6,7 +6,7 @@
 npm install -g @anthropic-ai/claude-code
 ```
 
-2. Obtain your `APTOS_BOT_KEY` by following the instructions [here](https://github.com/aptos-labs/aptos-npm-mcp?tab=readme-ov-file#generate-a-build-bot-api-key).
+2. Obtain your `APTOS_BOT_KEY` by following the instructions [here](https://github.com/aptos-labs/aptos-npm-mcp?tab=readme-ov-file#generate-a-geomi-bot-api-key).
 
 3. Navigate to your project
 

integration_guides/user_guide.md

@@ -24,13 +24,13 @@ Users should create proposals, vote once per wallet, view real-time results.
 Include a wallet integration for Aptos testnet."
 ```
 
-## Aptos Build Queries - Be Precise
+## Geomi Queries - Be Precise
 
 **Good Examples:**
 
-- "Get me all of my applications on Aptos Build"
+- "Get me all of my applications on Geomi"
 - "Create a new Full node API key resource named 'MyDApp-Production'"
-- "List all active API keys for my Build account"
+- "List all active API keys for my Geomi account"
 
 ## Perfect Prompt Template
 

package-lock.json

@@ -38,7 +38,7 @@
     "format": "prettier --write . && eslint --fix ."
   },
   "dependencies": {
-    "@aptos-labs/api-gateway-admin-api-client": "^2.1.0",
+    "@aptos-labs/api-gateway-admin-api-client": "^4.0.0",
     "dotenv": "^16.6.1",
     "fastmcp": "^1.27.3",
     "zod": "^3.24.4"

package.json

@@ -8,7 +8,7 @@ const GA_CLIENT_ID = process.env.GA_CLIENT_ID;
 
 // Aptos MCP configuration
 export const config = {
-  aptos_build: {
+  geomi: {
     adminUrl: "https://admin.api.aptoslabs.com/api/rspc",
     botKey: process.env.APTOS_BOT_KEY,
   },

src/config.ts

@@ -1,6 +1,6 @@
 # How to config a Full Node API Key for general blockchain interactions in an Aptos dapp
 
-Aptos full node api keys are designed as indentifications for authentication and rate limiting purposes. If you do not use an API key, your client will be considered “anonymous” and subject to significantly lower rate limits.
+Aptos full node api keys are designed as indentifications for authentication and rate limiting purposes. If you do not use an API key, your client will be considered "anonymous" and subject to significantly lower rate limits.
 
 The full node api key is used for general blockchain interactions when an applications wants to read data from chain or submit data to chain.
 
@@ -9,7 +9,7 @@ It is structured to enforce user validation steps before applying any modificati
 
 ### 🟩 Step 1: Retrieve & Display Available API Keys
 
-1. Fetch the user's Build Organizations, including:
+1. Fetch the user's Geomi Organizations, including:
 
 - Organizations
 - Applications
@@ -94,6 +94,6 @@ const aptos = new Aptos(
 - ✅ If mismatched, warn the user and ask for confirmation before proceeding.
 
 ### 🟩 Bonus: Documentation References
-[Build API Keys Guide](https://build.aptoslabs.com/docs/start/api-keys)
+[Geomi API Keys Guide](https://geomi.dev/docs/start/api-keys)
 
 ```

src/resources/how_to/how_to_config_a_full_node_api_key_in_a_dapp.md

@@ -9,7 +9,7 @@ It is structured to enforce user validation steps before applying any modificati
 
 ### 🟩 Step 1: Retrieve & Display Available GAS STATION API Keys
 
-1. Fetch the user's Build Organizations, including:
+1. Fetch the user's Geomi Organizations, including:
 
 - Organizations
 - Applications
@@ -102,6 +102,6 @@ import { aptosClient } from "../utils/aptosClient"; // this has our network defi
 - ✅ If mismatched, warn the user and ask for confirmation before proceeding.
 
 ### 🟩 Bonus: Documentation References
-[Build Gas Station Guide](https://build.aptoslabs.com/docs/gas-stations)
+[Geomi Gas Station Guide](https://geomi.dev/docs/gas-stations)
 
 ```

src/resources/how_to/how_to_config_a_gas_station_in_a_dapp.md

@@ -64,7 +64,7 @@ Ensure the configured API key network matches the network your dapp is using:
    - Common networks: `Network.MAINNET`, `Network.TESTNET`, `Network.DEVNET`
 
 2. **Verify API key network**:
-   - Check your Build console to see which network the API key was created for
+   - Check your Geomi console to see which network the API key was created for
    - API keys are network-specific and cannot be used across different networks
 
 ### 2.2 If Networks Don't Match
@@ -80,7 +80,7 @@ Ensure the configured API key network matches the network your dapp is using:
 
 If you have a properly configured API key but still experience rate limits:
 
-1. **Check your API key's rate limit settings** in the Aptos Build console:
+1. **Check your API key's rate limit settings** in the Geomi console:
 
    - Look for the `httpRateLimitPerIp` property
    - This determines how many requests per second your application can make
@@ -93,12 +93,12 @@ If you have a properly configured API key but still experience rate limits:
 
 If the current `httpRateLimitPerIp` is too low:
 
-1. **Navigate to your Aptos Build console**
+1. **Navigate to your Geomi console**
 2. **Select your API key**
 3. **Increase the `httpRateLimitPerIp` value** to a more appropriate level
 4. **Save the changes**
 
-⚠️ **Note**: Higher rate limits may incur additional costs depending on your Build plan.
+⚠️ **Note**: Higher rate limits may incur additional costs depending on your Geomi plan.
 
 ## 🟩 Step 4: Implement Rate Limit Error Handling in Code
 
@@ -162,5 +162,5 @@ Implement monitoring to track:
 
 ## 🟩 Additional Resources
 
-- [Aptos Build API Keys Guide](https://build.aptoslabs.com/docs/start/api-keys)
+- [Geomi API Keys Guide](https://geomi.dev/docs/start/api-keys)
 - [How to config a Full Node API Key in a dapp](./how_to_config_a_full_node_api_key_in_a_dapp.md)

src/resources/how_to/how_to_handle_rate_limit_in_a_dapp.md

@@ -1,17 +1,17 @@
-# How to Set Up No-Code Indexing with Aptos Build
+# How to Set Up No-Code Indexing with Geomi
 
-No-Code Indexing allows you to create real-time blockchain data indexers without writing custom indexing logic or managing/building infrastructure. Use it to query smart contract events in real-time for your dApp frontend.
+No-Code Indexing allows you to create real-time blockchain data indexers without writing custom indexing logic or managing/building infrastructure. Use it to query smart contract events in real-time for your dApp frontend. Geomi is the essential toolkit for Aptos developers.
 
 ## Prerequisites
 
 - Deployed Move smart contract with events on Testnet or Mainnet
 - Contract address and event structures
-- Aptos Build account
+- Geomi account
 
-## Project Setup in Aptos Build
+## Project Setup in Geomi
 
-1. **Create processor in Aptos Build**:
-   - Go to [Aptos Build](https://build.aptoslabs.com/) and sign in
+1. **Create processor in Geomi**:
+   - Go to [Geomi](https://geomi.dev/) and sign in
    - Click "Create New Project" → "Processor"
    - Name your project (3-32 characters, lowercase, numbers, `_` or `-`)
 
@@ -55,7 +55,7 @@ query {
 ```
 
 4. **Get API credentials**:
-   - Return to Aptos Build → your project → API Keys
+   - Return to Geomi → your project → API Keys
    - Copy API key (starts with `aptoslabs_...`)
    - Note processor ID from API URL
 
@@ -262,3 +262,4 @@ curl -X POST https://api.testnet.aptoslabs.com/nocode/v1/api/YOUR_PROCESSOR_ID/v
    - **GraphQL errors**: Check table and column names match exactly
 
 Replace `your_table_name` with your actual table name and adjust column names to match your event structure.
+