> For the complete documentation index, see [llms.txt](https://agpt.co/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://agpt.co/docs/integrations/block-integrations/websets_team.md).

# Exa Websets Team

Blocks for checking your team's Exa Websets capacity.

## Exa Get Websets Team Info

### What it is

Get your team's Websets concurrency usage and limits, to check capacity before launching large websets

### How it works

This block reads the Websets API's `/v0/teams/me` and returns how many requests are active and queued against the team's concurrency and queue limits. An empty limit means unlimited.

`available_slots` is max concurrent minus active (never below 0), and `has_capacity` is true when a slot is free or there is no limit; it does not consider the queue. It charges only if Exa's response reports a cost (150 credits per USD).

### Outputs

| Output           | Description                                                                              | Type |
| ---------------- | ---------------------------------------------------------------------------------------- | ---- |
| error            | Error message if the operation failed                                                    | str  |
| team\_id         | The team's unique identifier                                                             | str  |
| name             | The team's name                                                                          | str  |
| active           | Websets requests being processed right now                                               | int  |
| queued           | Websets requests waiting to start                                                        | int  |
| max\_concurrent  | Most requests the team can run at once (empty means unlimited)                           | int  |
| max\_queued      | Most requests the team can queue (empty means unlimited)                                 | int  |
| available\_slots | Requests that can start immediately: max concurrent minus active (empty means unlimited) | int  |
| has\_capacity    | True if a new request would start now instead of queueing                                | bool |

### Possible use case

**Pre-Launch Check**: Confirm there is a free slot before creating a large webset.

**Backoff Logic**: Wait and retry later when has\_capacity is false instead of adding to the queue.

**Usage Monitoring**: Track active and queued requests over time to see whether the plan's limits are enough.

***


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://agpt.co/docs/integrations/block-integrations/websets_team.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
