Get the inbox data you need. Leave the rest private.

bind.co is email context infrastructure for applications and AI agents. With the user’s permission, it turns inbox information into structured business records, such as contacts, relationships and expenses. Those records stay current as new email arrives, and your application receives only what the user approves.

No. Your app doesn’t get access to users’ mailboxes, and email messages don’t cross the API. bind.co processes the inbox on its side and returns structured records within the permissions users approve.

You can, and it will demo well. Production is harder. The same fact appears across many threads, values change over time, document versions conflict, and user corrections have nowhere to persist, so the next run can contradict them. You also take on OAuth app verification, CASA, provider rate limits and ongoing maintenance.

bind.co maintains one reconciled record across the whole inbox, so your agent queries facts instead of re-reading email each time.

Depending on approved permissions:

• Contacts and relationships: People, organizations, inferred roles, relationship strength and communication history.
• Business records: Document classifications, extracted fields and structured records such as expenses, invoices, receipts and payroll change requests.
• Drafts: Personalized emails written toward a goal your app sets, informed by relationship history.

Inferred values include confidence scores and source references where applicable. Full schemas are in the API docs.

Pricing depends on the number of connected inboxes, the capabilities you use and the amount of processing required. If you’re evaluating bind.co or planning a larger integration, talk to a founder about your use case.

Email APIs return messages, threads and attachments, and turning those into usable data is left to you. bind.co returns maintained business records, such as contacts, relationships and expenses, within the permissions the user approved. You can also run bind.co alongside an existing email integration.

Software companies adding inbox context to existing products, developers building new applications, and AI agent builders who need context their agents can reliably act on. Agencies also use bind.co to build for clients.

Our initial focus is software serving small and midsize businesses in relationship-driven work, such as accounting, practice management, CRM, accounts payable, expense management and field services.

bind.co reconciles information across the inbox, resolves duplicates and keeps records current as new information arrives. Because answers come from maintained records, the same question returns the same answer unless the underlying information changes.

Inferred values include confidence scores and supporting evidence, so your app can decide what to trust and what needs review. User-confirmed values are preserved rather than silently overwritten by new AI-generated suggestions.

Your app sets a goal, such as following up with prospects, re-engaging past clients, requesting a review or chasing a missing document. bind.co then drafts a personalized email for each relevant contact, informed by relationship history. You can pass in additional context to sharpen the drafts.

Users review and edit before anything is sent, and sending requires a separate permission.

Your app can pass in additional context, such as customer details, meeting notes or instructions. We can also work with you on custom record types, documents and sources beyond the inbox. Talk to a founder about what you’re building and we’ll help determine what’s possible.

bind.co is SOC 2 Type II audited and has completed a CASA Level 2 assessment. Data is encrypted in transit and at rest. Applications receive only the information users authorize, not access to their mailboxes. You can review our security documentation in the Trust Center.

No. bind.co does not use customer data to train AI models and does not sell customer data.

Your app requests permissions for a defined use case. The user connects their Google (Gmail) or Microsoft (Outlook) mailbox through bind.co and approves what your app can receive. Sending email requires a separate permission.

When a user revokes access, API access under that authorization stops and your app is notified by webhook. Users can also request deletion of their data, as described in our Privacy Policy.

bind.co is hosting on the Google Cloud Platform in US Data centres. If you have additional region and data residency requirements, contact us.

Users control which apps are authorized. bind.co is responsible for protecting data within its infrastructure. Once your app receives records, your use, storage and retention of them are governed by your own policies and privacy obligations.

Users see bind.co when they connect their inbox and approve what your app can receive, and they can manage their authorizations through bind.co. There is no separate app for them to use day to day.

Records become available as bind.co processes the inbox, so you can start using results before historical processing finishes. Processing time depends on inbox size and the information requested. New email is processed as it arrives, and webhooks notify your app when relevant records change.

bind.co supports Google (Gmail) and Microsoft (Outlook) inboxes through one API, with the same consent model and response shape for both. For shared mailboxes, specific account types or other providers, contact us.

bind.co holds the Gmail and Outlook connection and has completed the CASA assessment for that access. Your app goes through bind.co’s app review instead. If your own compliance program has additional requirements, talk to a founder.

bind.co is a REST API with an OpenAPI specification, documentation and webhooks. The docs are also published in Markdown with an llms.txt index, so you can work with them directly in AI coding tools.

Create a developer account, register your app and submit it for review. Reviews are typically completed the same business day. Once approved, connect your own inbox and test against the live API.

The Quickstart walks you through your first call.