botdoc.io valid

Botdoc

Botdoc invented Secure Digital Transport (SDT) - a new category for moving sensitive data into and out of any system without anyone logging in. Patented in 6 jurisdictions (US, EU, UK, Canada, Australia, Japan, India). The SDT Engine is the underlying technology. External Automation Projects (EAPs) like SecureMFP, Connect, Lite, ID Verify, and Secure Messaging are products Botdoc built on the Engine. Third Party Integrations (TPIs) like Salesforce SDT (Cloud Maven), SDX (Edward Jones), and VedaP

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-25T20:06:17.012Z. Cached copy · Source on botdoc.io

# Botdoc

> Botdoc invented Secure Digital Transport (SDT) - a new category for moving sensitive data into and out of any system without anyone logging in. Patented in 6 jurisdictions (US, EU, UK, Canada, Australia, Japan, India). The SDT Engine is the underlying technology. External Automation Projects (EAPs) like SecureMFP, Connect, Lite, ID Verify, and Secure Messaging are products Botdoc built on the Engine. Third Party Integrations (TPIs) like Salesforce SDT (Cloud Maven), SDX (Edward Jones), and VedaPointe.Send for EPIC are partner products built on the Engine. Legal entity: ShortSave, Inc. DBA Botdoc.

## The category: Secure Digital Transport (SDT)

- [What is SDT? Secure Digital Transport defined](https://botdoc.io/sdt/) - the canonical definition, three pillars, and the volatile-vs-secure paradox SDT resolves
- [SDT Engine - developer access to Secure Digital Transport](https://botdoc.io/sdt-engine/) - token-based REST API, sandbox, white-label, P2 capabilities
- [Botdoc patents portfolio](https://botdoc.io/patents/) - 7 patents granted in US, EU, Canada, Australia, Japan, India
- [Built on the SDT Engine - catalog of products and integrations](https://botdoc.io/built-on-sdt/) - EAPs and TPIs index

## External Automation Projects (EAPs - products Botdoc built)

- [SecureMFP - scan-to-delivery for regulated MFP fleets](https://botdoc.io/built-on-sdt/securemfp/) - replaces scan-to-email with end-to-end encrypted transport
- [Connect - CRM-integrated dealership secure communication](https://botdoc.io/built-on-sdt/connect/) - used by automotive dealers nationwide
- [Lite - secure messaging for smaller dealers and franchise groups](https://botdoc.io/built-on-sdt/lite/) - on-demand secure text and email
- [ID Verify - real-time driver's-license and identity verification](https://botdoc.io/built-on-sdt/id-verify/) - sub-3-second flow, 94% success rate
- [SecureMyDealer - automotive EAP family](https://botdoc.io/built-on-sdt/securemydealer/) - Connect + Lite + ID Verify under one brand

## Third Party Integrations (TPIs - partner products built on SDT)

- [Secure File Transport for Salesforce by Cloud Maven](https://botdoc.io/built-on-sdt/salesforce-sdt/) - AppExchange plugin, "Powered by Botdoc" attribution
- [SDX by Edward Jones - financial-advisor secure document workflow](https://botdoc.io/built-on-sdt/sdx/) - public user guide OLM-16043B-A
- [VedaPointe.Send for EPIC - HIPAA-compliant patient communication](https://botdoc.io/built-on-sdt/vedapointe-send/) - fax-killer integrated directly into EPIC EMR

## SDT Engine capabilities (P2 - second-level platform features)

- [P2 ID Verification - government-issued ID verification capability](https://botdoc.io/sdt-engine/p2-id-verification/)
- [P2 ID Capture - driver's-license front and back capture](https://botdoc.io/sdt-engine/p2-id-capture/)
- [P2 Payment Collection - payment-method capture without storing card data](https://botdoc.io/sdt-engine/p2-payment-collection/)
- [P2 Push Pull - bidir
…

Machine-readable: GET /v1/resolve?q=botdoc.io · GET /v1/domain/botdoc.io · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for botdoc.io:
1. POST https://agentwebmap.com/v1/sites/botdoc.io/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://botdoc.io/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/botdoc.io/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/botdoc.io).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.