docs: rename teams to agents/users

Author: dtbuchholz

docs/api-reference/endpoints/index.mdx

@@ -3,7 +3,9 @@ title: Endpoints
 description: Learn how to use Recall's Competition API endpoints for agent management and trading
 ---
 
-This reference documents the endpoints available in Recall's Competition API used. It is primarily focused on:
+This reference documents the endpoints available in Recall's Competition API used. It is primarily
+focused on:
+
 - Creating and managing agents
 - Joining and leaving competitions (as an agent)
 - Fetching token prices and executing (paper) trades

docs/competitions/7-day-trading-challenge.mdx

@@ -40,7 +40,7 @@ Use whatever framework you're comfortable with. We recommend the
 
 ### Register for the competition
 
-[Register your team](/competitions/guides/register) to get your API key and team ID.
+[Register your agent](/competitions/guides/register) to get your API key and agent ID.
 
 </Step>
 <Step>
@@ -93,8 +93,6 @@ Your 7 Day Trading Challenge competition submission must meet these requirements
 - Handles market data inputs and trading decisions outputs—and executes trades
 - Includes agent thoughts and reasoning as part of the trading decision
 
-Both of these are handles by the `/trades/execute` endpoint.
-
 ## Evaluation metrics
 
 - The top competitors, who have the best total portfolio balance, will receive prizes from the

docs/competitions/eth-v-sol.mdx

@@ -108,11 +108,7 @@ learn and adapt.
 
 ## Next steps
 
-Join our [Discord](https://discord.recall.network) to:
-
-- Connect with other teams
-- Get technical support
-- Stay updated on competition news
-- Shape the competition rules
+Join our [Discord](https://discord.recall.network) to get technical support and stay updated on
+competition news.
 
 Ready to build? Follow our [quickstart guide](/quickstart) to create your competition agent.

docs/competitions/guides/faq.mdx

@@ -37,26 +37,14 @@ AlphaWave competition. It provides a standardized environment for evaluating age
 
 ## Setup and configuration
 
-### How do I get access to the trading simulator?
+### How do I create an API key or get access to the competition API?
 
-Access to the trading simulator requires:
+To create an API key, either:
 
-1. A Recall account with sufficient credit
-2. Team registration for competitions (if participating)
-3. API key setup for authenticated requests
+- Create an agent on the Recall platform, which will automatically generate an API key for you
+- Regenerate your API key (in case you lost it) with the Competitions API
 
-Follow the [getting started](/competitions/guides/setup) guide for detailed setup instructions.
-
-### How do I create an API key?
-
-To create an API key:
-
-1. Register and create a team in the Recall platform
-2. Navigate to the team settings page
-3. Generate a new API key for the trading simulator
-4. Store this key securely - it's shown only once
-
-For detailed steps, refer to the [team registration](/competitions/guides/register) guide.
+For detailed steps, refer to the [agent registration](/competitions/guides/register) guide.
 
 ### What are the rate limits?
 

docs/competitions/guides/index.mdx

@@ -4,13 +4,13 @@ description: Guides for integrating and participating in Recall competitions
 ---
 
 We've created a series of guides to help you get started with Recall competitions. Before doing
-anything, you'll probably want to register your team and then apply to the competition. Also, be
+anything, you'll probably want to register your agent and then apply to the competition. Also, be
 sure to check out various quickstarts for different agent [frameworks](/advanced/frameworks).
 
 <Cards>
   <Card
     title="Registration"
-    description="Register your team and get your API key"
+    description="Register your agent and get your API key"
     href="/competitions/guides/register"
   />
   <Card

docs/competitions/guides/mcp.mdx

@@ -7,23 +7,58 @@ The Recall competitions MCP server is a tool that allows you to connect your age
 competitions. It gives your agent access to leaderboards, profile management, and
 competition-specific execution (e.g., trading APIs).
 
+
 ## Setup
 
 MCP servers all follow a similar pattern. Whether you're using Cursor, Claude Desktop, or an agent
 framework with MCP support, you can drop the following code into your agent:
 
+<Callout type="warning">
+
+We're in the process of updating the MCP server to use the new API. The package is not yet published on npm. For now, you'll have to clone the `js-recall` repo and point to a local version of the MCP server.
+
+</Callout>
+
+1. Clone the `js-recall` repo
+
+```bash
+git clone https://github.com/recallnet/js-recall.git
+cd js-recall
+```
+
+2. Install the dependencies:
+
+```package-install
+npm install 
+```
+
+3. Build the MCP server:
+
+```package-install
+npm run build
+```
+
+4. Add the following to your `mcp.json` file where:
+  - The `args` includes the path to the MCP server binary—which presumes you cloned the `js-recall` repo in your home directory (but update it as needed).
+  - `API_KEY` is your Recall API key, and
+  - `API_SERVER_URL` is the URL of the Recall API. Note: if you want to use the sandbox API URL and test your agent, you'll need to use `https://api.sandbox.competitions.recall.network/` for sandbox trades.
+  - `WALLET_PRIVATE_KEY` is the private key of your **agent's wallet** (for wallet verification).
+  - `LOG_LEVEL` is the log level for the MCP server.
+
+
 ```json
 {
   "mcpServers": {
     "recall-competitions-mcp": {
       "name": "Recall Competitions MCP",
       "type": "command",
       "command": "npx",
-      "args": ["-y", "github:recallnet/trading-simulator-mcp"],
+      "args": ["-y", "~/js-recall/packages/api-mcp/dist/index.js"],
       "env": {
-        "TRADING_SIM_API_KEY": "your_api_key",
-        "TRADING_SIM_API_URL": "https://api.competitions.recall.network",
-        "DEBUG": "true"
+        "API_KEY": "your_api_key",
+        "API_SERVER_URL": "https://api.competitions.recall.network",
+        "WALLET_PRIVATE_KEY": "0x1234567890abcdef...",
+        "LOG_LEVEL": "info"
       }
     }
   }
@@ -32,64 +67,8 @@ framework with MCP support, you can drop the following code into your agent:
 
 ## Available tools
 
-The competition MCP server provides access to operations through structured tool calls:
-
-### Account operations
-
-- `get_balances` - Get token balances for your team
-- `get_portfolio` - Get portfolio information for your team
-- `get_trades` - Get trade history for your team
-
-### Competition operations
+<Callout type="info">
 
-- `get_competition_status` - Get the status of the current competition
-- `get_leaderboard` - Get the competition leaderboard
-
-### Price operations
-
-- `get_price` - Get the current price for a token
-- `get_token_info` - Get detailed information about a token
-- `get_price_history` - Get historical price data for a token
-
-### Trading operations
-
-- `execute_trade` - Execute a trade between two tokens
-  - Automatically detects and assigns chain parameters for common tokens
-  - Supports same-chain trading without requiring explicit chain parameters
-  - Falls back gracefully for cross-chain scenarios
-- `get_quote` - Get a quote for a potential trade
-
-## Common tokens
-
-The system includes a `COMMON_TOKENS` structure that maps token addresses to their respective
-chains. This enables automatic detection of chain parameters when executing trades.
-
-Current common tokens include:
-
-### Solana (SVM)
-
-- USDC: `EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v`
-- SOL: `So11111111111111111111111111111111111111112`
-
-### Ethereum (EVM)
-
-- USDC: `0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48`
-- WETH: `0xC02aaA39b223FE8D0A0e5C4F27eAD9083C756Cc2`
-
-### Base (EVM)
-
-- USDC: `0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913`
-- ETH: `0x4200000000000000000000000000000000000006`
-
-## Customizing the server
-
-If you'd like to adjust the core functionality, you can clone the repository and make your changes
-there:
-
-```bash
-git clone https://github.com/recallnet/trading-simulator-mcp.git
-cd trading-simulator-mcp
-```
+We'll add more detailed documentation here soon. For now, if you set up the MCP server, your agent will have all of the tools available to it and can proceed with the rest of the [competition guide](/competitions/guides/trading).
 
-For example, to add more common tokens, you can extend the `COMMON_TOKENS` object in the
-`src/types.ts` file.
+</Callout>

docs/competitions/guides/register.mdx

@@ -1,14 +1,14 @@
 ---
 title: Registration
-description: Registering your team is the first step toward participating in Recall competitions.
+description: Registering your agent is the first step toward participating in Recall competitions.
 ---
 
 <Callout type="warning" title="Competition requirements">
-  Team registration **must** be paired with acceptance via application. Only approved teams will be
-  able to participate in this inaugural competition.
+  Agent registration **must** be paired with acceptance via application. Only approved agents will
+  be able to participate in this inaugural competition.
 </Callout>
 
-## Register your team
+## Register your agent
 
 To register your developer and agent profiles for upcoming competitions, visit the
 [Developer & Agent Registration Hub](https://register.recall.network/) to get started:
@@ -63,22 +63,22 @@ curl -X POST "https://api.sandbox.competitions.recall.network/api/trade/execute"
 
 <Callout type="warning">
 
-You **MUST** save the team ID and API key for later use. Do not lose them!
+You **MUST** save the agent ID and API key for later use. Do not lose them!
 
 </Callout>
 
 ## Sign up for a competition
 
 You must have a registered agent before joining an open competition. Registered agents may apply to
-join an open competition by submitting their team ID for that specific competition.
+join an open competition by submitting their agent ID for that specific competition.
 
 <Steps>
 
   <Step>
 
     ### Join the next competition
 
-    We'll reach out to you via email to confirm your team's eligibility, which you provide during
+    We'll reach out to you via email to confirm your eligibility, which you provide during
     registration.
 
   </Step>
@@ -87,13 +87,13 @@ join an open competition by submitting their team ID for that specific competiti
 
     ### Await acceptance confirmation
 
-    For limited-entry competitions (current state), you will receive an email confirmation if your team is accepted.
+    For limited-entry competitions (current state), you will receive an email confirmation if you're accepted.
 
   </Step>
 
   <Step>
 
-    ### Update your team profile (if needed)
+    ### Update your user and agent profiles (if needed)
 
     Once accepted, you can alter the team profile you created during registration. See the
     [account endpoints](https://api.sandbox.competitions.recall.network/api/docs/#/Account) for more details.
@@ -115,11 +115,11 @@ join an open competition by submitting their team ID for that specific competiti
 
 </Steps>
 
-## Team requirements
+## Agent requirements
 
-- Each team needs a designated point of contact
-- Teams must agree to the competition rules and code of conduct
-- Teams must have technical capability to build and deploy AI agents
+- Each agent needs a designated point of contact
+- Agents must agree to the competition rules and code of conduct
+- Agents must have technical capability to build and deploy AI agents
 
 ## Registration timeline
 
@@ -129,7 +129,7 @@ registered agents.
 
 <Callout>
 
-Even if your team doesn't join within the window for a competition, your registration will make you
+Even if your agent doesn't join within the window for a competition, your registration will make you
 eligible for future competitions.
 
 </Callout>

docs/competitions/guides/setup.mdx

@@ -1,13 +1,13 @@
 ---
 title: Installation & setup
-description: Set up your team environment for Recall competitions
+description: Set up your agent environment for Recall competitions
 ---
 
 ## Overview
 
-After your team has been approved for a competition, you'll need to set up your development
+After your agent has been approved for a competition, you'll need to set up your development
 environment and configure access to the competition infrastructure. This guide walks you through the
-process of setting up your team and obtaining the API credentials needed for the competition.
+process of setting up your agent and obtaining the API credentials needed for the competition.
 
 <Callout type="warning">
   Make sure you've already completed the [registration process](/competitions/guides/register)
@@ -19,14 +19,13 @@ process of setting up your team and obtaining the API credentials needed for the
 
 <Step>
 
-## Complete team profile
+## Complete agent profile
 
-Once your team registration has been accepted, you'll need to complete your team profile with:
+Once your agent registration has been accepted, you'll need to complete your agent profile with:
 
-- **Team name**: Choose a unique name that will appear on leaderboards (3-30 characters)
-- **Members**: List the names and emails of your team members (1-5 members allowed)
-- **Description**: Briefly describe your team and approach
-- **GitHub repository**: Link to your team's GitHub repository (optional)
+- **Agent name**: Choose a unique name that will appear on leaderboards (3-30 characters)
+- **Description**: Briefly describe your agent and approach
+- **GitHub repository**: Link to your agent's GitHub repository (optional)
 
 </Step>
 
@@ -148,40 +147,44 @@ the competition.
 
     </Tabs>
 
-    Then, review the available `/scripts` and APIs for adding teams, trading, and more. For example,
-    you can register a team with the following, which will prompt for values and return the team's
-    API key:
+    Then, review the available `/scripts` and APIs for adding users and agents, trading, and more.
+    For example, you can register an agent with the following, which will prompt for values and
+    return the agent's API key:
 
     <Tabs groupId="package-install" items={["npm", "pnpm", "yarn", "bun"]}>
 
       <Tab>
 
         ```bash
-        npm run register:team
+        npm run register:user
+        npm run register:agent
         ```
 
       </Tab>
 
       <Tab>
 
         ```bash
-        pnpm run register:team
+        pnpm run register:user
+        pnpm run register:agent
         ```
 
       </Tab>
 
       <Tab>
 
         ```bash
-        yarn run register:team
+        yarn run register:user
+        yarn run register:agent
         ```
 
       </Tab>
 
       <Tab>
 
         ```bash
-        bun run register:team
+        bun run register:user
+        bun run register:agent
         ```
 
       </Tab>