# Connect external integrations

Use the marketplace to find the right protocol, tool name and deployment owner for a service. Text stats and Text cleaning are built-in profiles. Other listings describe integrations that run on their own infrastructure.

## Choose a shelf

| Shelf | Examples | First check |
|---|---|---|
| Data | Text cleaning, Text stats, S3 explorer, Document chunking, Corpus snapshots | Read the availability badge. Only the two built-ins run as Hub-managed profiles. |
| Social | Telegram archives | Export an authorized Telegram Desktop chat as JSON and use the archive processor's upload endpoint. |
| LLMs | Model providers | Use the configured provider and its own authorization. |
| Transcription | Audio transcription, Video transcription | Upload permitted media to the selected service. Use its upload ID when submitting a job. |
| Search | Text embeddings, Qdrant search | Confirm that the model or collection is prepared on the target host. |
| Developer tools | Hub API, Recipe runs | Read the listing to distinguish the Hub control surface from an independently provisioned recipe service. |

Search by tool or service name and open **Connection guide** to inspect a card's setup, access, tools, endpoints and synthetic example. For Telegram, voice and video, the service accepts the source file, returns an upload ID and exposes job status and result pages. Keep file bytes and service credentials on the intended endpoint.

## Connect S3 from a service card

1. Open `daedro-s3` and prepare the image pinned by digest in its manifest. The launcher uses that preloaded image.
2. Create a dedicated credential file outside Git with read access limited to the selected buckets. Inject `DAEDRO_S3_ENV_FILE` and `DAEDRO_S3_ENDPOINT` into the S3 MCP process.
3. Configure a separate client entry to run `/bin/sh` with the absolute path to `integrations/s3/launch.sh`. Restrict the client to the manifest's five tools. Read the [S3 connection guide](../integrations/s3/README.md) before selecting an object.

The hub needs no S3 keys to describe the service. A successful catalog lookup confirms the presence of a card. Test authorized object access separately with `s3_get_object` and an approved bucket and key.

To read the same contract programmatically, use `service_get` over MCP or `GET /api/v1/services/daedro-s3` on the Hub. [Client examples](clients.md) · [Live reference](reference.md)