> ## Documentation Index
> Fetch the complete documentation index at: https://docs.deck.co/llms.txt
> Use this file to discover all available pages before exploring further.

# Sources

> A source is any software your agents connect to.

A source is a website your agents connect to. Provide a URL, and Deck handles the rest.

Sources belong to your organization and can be shared across agents and tasks. Your "Hilton" source works for both a reservations agent and an expense report agent.

## How sources fit in

Sources are the "where" of Deck. [Credentials](https://docs.deck.co/concepts/credentials.md) authenticate a user to a source. Once connected, [tasks](https://docs.deck.co/concepts/tasks.md) execute against that source through the credential.

There is no coupling between sources and agents. If two agents need to connect to the same website, use the same source.

## Creating a source

Sources can be created from the Console or through the API. A source behind an access gateway can carry [custom headers](https://docs.deck.co/platform/source-headers.md) that Deck attaches on every request to it. A source that only accepts allowlisted IP addresses can use [static IPs](https://docs.deck.co/platform/static-ips.md), so every run against it comes from a fixed range.

## Resetting a source

When you create a source, Deck analyzes its antibot defenses and uses that analysis on every run. Sources change their defenses over time, so a source that worked before can start failing with `blocked` errors.

If that happens, reset the source by calling [`POST /sources/{source_id}/reset`](https://docs.deck.co/api-reference/sources/reset-a-source). Deck analyzes the source again; runs keep using the existing analysis until the new one is complete. Resetting again shortly after a previous reset has no effect. Check `reset_at` on the response to see when the last reset took effect.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.