> ## Documentation Index > Fetch the complete documentation index at: https://docs.darwin.so/llms.txt > Use this file to discover all available pages before exploring further. # Connect > Bring Darwin into an application without sharing an account credential. Connect lets an application use Darwin for its own users. The application manages configuration and webhooks; each end user authorizes the access it needs. Search and Act remain the same capabilities whether a request starts in Darwin or in your product. ## How it works 1. Register an application and configure its server-side credentials. 2. Link a user through Darwin's authorization flow. 3. Send requests with verified application and user context. 4. Receive status and results through the API or webhooks. An application cannot choose an arbitrary Darwin `user_id` and act on that person's behalf. Darwin checks the live grant and scopes for every operation. ## API The [API Reference](/reference/introduction) documents the live `/api/v2/connect` contract for applications, linked AIs, enrollment, service accounts, and webhooks. Application-initiated goals belong to Act; application wallets belong to Account. List applications you own with a server-side user key that has applications read access: ```bash theme={null} curl https://api.darwin.so/api/v2/connect/applications \ -H "Authorization: Bearer $DARWIN_API_KEY" ``` ## Permissions and approvals This request uses an owner key with applications read access. An application credential has narrower powers: a user must be linked through a verified grant, and the requested operation must fit its scopes. The application cannot gain authority by sending a user ID. ## Pricing Connect's displayed monthly call limits are **proposed**; final capacity is confirmed for your application. Act and Darwin-hosted AI usage are billed separately. See [current pricing](https://darwin.so/pricing) and confirm costs before billable work for users. Use REST or an SDK from a trusted server.