Box

Files and knowledge

Box for AI agents. Managed auth, ready-made tools.

Search, read, upload and organize files and folders in Box on behalf of each of your users.

About Box

With the Box connector, your agent works in each user’s own Box account. It can search files, list what is in a folder, read file details, download or upload a file, create a folder and comment on a file, using only the tools your project allows.

Box is a cloud content platform for storing, sharing and managing files.

Tools

What your agent can do in Box.

Each tool is a capability the model can call. You decide which ones a project allows, and every call runs with the end user's own Box connection.

  • Search files

    Read
    box_search

    Search files and folders the user can access.

  • List folder items

    Read
    box_list_folder_items

    List the files and folders inside a folder.

  • Get file details

    Read
    box_get_file

    Get a file's name, size, owner and dates.

  • Download a file

    Read
    box_download_file

    Download the contents of a file.

  • Upload a file

    Write
    box_upload_file

    Upload a new file to a folder.

  • Create a folder

    Write
    box_create_folder

    Create a folder inside another folder.

  • Add a comment

    Write
    box_add_comment

    Comment on a file.

Control

Limits you can set.

You decide what your agent may do in Box, and Agent200 runs every call within those limits.

  • Turn single tools on or off

    Let the agent search and read files, and switch off box_upload_file so it can never add a file.

  • Restrict what the agent reaches

    Choose the endpoints and scopes a project may use, for example reading files but not uploading them. A call outside them is refused.

Get started

Connect Box
in three steps.

  1. 1

    Set up the SDK

    Add the Agent200 SDK to the codebase you already have and authenticate with your API key. The key covers every connector enabled for the project.

    agent.js
    Conceptual example
    Set up the SDK with the Agent200 API key
    // One Agent200 API key covers every connector enabled for the project.
    const agent200 = new Agent200({
      apiKey: process.env.AGENT200_API_KEY,
    });
  2. 2

    Let your user connect Box

    Each end user authorizes their own Box account once. Agent200 runs the OAuth flow, handles the callback, stores the tokens and refreshes them.

    connect.js
    Conceptual example
    Let an end user connect their account (managed OAuth)
    // Each end user authorizes their own Box account, once.
    const connection = await agent200
      .user("user_123")
      .connect("box");
    
    if (connection.authorizationUrl) {
      // Show this link to your user; Agent200 handles the rest.
      console.log(connection.authorizationUrl);
    }
  3. 3

    Run with the Box tools

    Name the user, the model and the tools. The model decides which Box tools to call, and Agent200 executes them with that user's connection.

    run.js
    Conceptual example
    Run a request with the connector's tools
    const result = await agent200
      .user("user_123")
      .run({
        model: "openai/gpt-5.6-sol",
        input: "Find the latest signed contract in my Box",
        tools: ["box"],
      });
    
    console.log(result.output);

Access

Sign-in and permissions.

  • Who signs in

    Each of your users, once, on Box's own sign-in page. You never see or store their Box password.

  • What access is requested

    The scopes the connection needs, such as reading all files and folders or reading and writing them, listed on Box's authorization screen. Users can remove the app later from their Box account settings.

For agents

Instructions for AI agents.

Using a coding agent? Paste this brief into it, or give it the address of this page. It describes the Box connector and how to use it.

Agent brief
Connector: Box, through Agent200. In code: "box".
What it does: Search, read, upload and organize files and folders in Box on behalf of each of your users.
Page: https://www.agent200.com/connectors/box/

1. Get an Agent200 API key. If the developer has none, send them to https://agent200.com/platform/apikeys/ and ask them to choose "Create an API key". Read the key from the AGENT200_API_KEY environment variable. Never ask for it in chat, and never write it into code, prompts or logs.
2. Sign-in is managed OAuth. Each end user approves access once, on Box's own page, through the authorization link Agent200 returns. Never ask a user for a Box password or token in chat.
3. Give every request a stable id for the end user. Agent200 uses only that user's own connection.
4. Read tools: box_search, box_list_folder_items, box_get_file, box_download_file. Write tools: box_upload_file, box_create_folder, box_add_comment. Name "box" in the tools of a request; the model decides which tool to call.
5. Stay within the project's settings. If a tool is turned off or a call is refused, tell the user. Do not work around it.
6. Before a write, confirm with the user, unless they asked for that exact change.
7. For setup with a specific framework, follow its guide:
   https://www.agent200.com/connectors/box/framework/claude/
   https://www.agent200.com/connectors/box/framework/chatgpt/
   https://www.agent200.com/connectors/box/framework/claude-code/
   https://www.agent200.com/connectors/box/framework/muse/
   https://www.agent200.com/connectors/box/framework/grok-bot/
   https://www.agent200.com/connectors/box/framework/openai-dots/
   https://www.agent200.com/connectors/box/framework/claude-duet/
   https://www.agent200.com/connectors/box/framework/hermes-agent/
   https://www.agent200.com/connectors/box/framework/openclaw/

The code on the connector page is a conceptual example of the SDK. SDK reference: https://docs.igpt.ai/

This page is also available as Markdown, for agents and LLMs: /connectors/box.md

Guides

Use Box with the AI you build on.

Step-by-step setup for Box with a specific model, assistant or agent framework.

FAQ

Box and Agent200, answered.

Who handles the Box OAuth flow and the tokens?

Agent200. It runs the authorization, handles the callback on its own domain, stores the tokens and refreshes them. You do not build or maintain an OAuth integration for Box.

Does my agent act as the end user?

Within what that user authorized, yes. Every request names an end user, and Agent200 uses only that user's Box connection, never another user's. It cannot reach anything the user or Box has not authorized.

Can I limit what my agent can do in Box?

Yes. You choose which services, endpoints and authorization scopes are allowed in your Agent200 configuration, and the agent works only within them.

  • Google Drive

    Google Drive

    Find, read and organize the files in each user's Drive.

    Managed OAuth Files and knowledge
  • OneDrive

    OneDrive

    Search, read, upload and share OneDrive files, including Word, Excel and PowerPoint documents, on behalf of each of your users.

    Managed OAuth Files and knowledge
  • Dropbox

    Dropbox

    Search, read, upload and organize Dropbox files, and create shared links, on behalf of each of your users.

    Managed OAuth Files and knowledge
  • Notion

    Notion

    Search, read and write Notion pages and databases on behalf of each of your users.

    Managed OAuth Files and knowledge
200 OK

Start with Box.
Your agent does the rest.

Your users connect their own Box accounts. Agent200 handles the OAuth, the tokens and every tool call.

Book a demo.
See it in action.

Tell us who you are, then pick a time for a 1:1 session with an expert from our team.

We use your details only to email you about Agent200. See the Privacy Policy.

Pick a time. We'll take it from there.

A 1:1 session with an expert from our team, about what you are building.

Open in Calendly (opens in a new tab)