scrambleid.com valid

ScrambleID: llms.txt

This file helps AI engines (ChatGPT, Perplexity, Claude, Google AI Overviews, Bing Copilot) understand ScrambleID's content and cite it accurately. Last updated: 2026-06-11.

For agents: ScrambleID offers cryptographic identity authentication replacing shared secrets, with OIDC/SAML, REST APIs and iOS/Android/Web SDKs for enterprises.

cryptographic identityworkforce authenticationoidc samlvishing preventioniamidentity governance

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-20T23:03:03.803Z. Cached copy · Source on scrambleid.com

# ScrambleID: llms.txt

> This file helps AI engines (ChatGPT, Perplexity, Claude, Google AI Overviews, Bing Copilot) understand ScrambleID's content and cite it accurately. Last updated: 2026-06-11.

## What ScrambleID Is

ScrambleID is the trust infrastructure for humans, machines, and the agents they deploy. The platform is organized as three products under one cryptographic proof rail. Humans gives you identity and accountability across every channel a human reaches you through: Workforce (passwordless web auth for employees), Contact Center (caller authentication replacing KBA and vishing-resistant), Frontline (shared-device passwordless for retail, healthcare, and POS), and People (person-to-person verification via Trust Checks). The same primitive deploys across B2B, D2C (consumer-facing One Tap / QR / Type Code / Passkey), and enterprise rollout models, so consumer-facing passwordless is a deployment of the four channels, not a separate channel. Non-humans gives you identity and accountability for AI agents, machines, bots, and the broader non-human estate. Actions gives you per-action authorization and an audit chain that names every signer on every transaction. ScrambleID layers on top of existing identity providers (Okta, Microsoft Entra ID, Ping Identity, ForgeRock) and CIAMs (Auth0, Okta CIC, Stytch, ForgeRock CIAM). No rip and replace. Typical deployment takes two weeks.

## Key Products

- **Humans**: Identity and accountability across every channel a human reaches you through: workforce, contact center, frontline, and people-to-people. Four channels, one cryptographic primitive, deployed across B2B, D2C, and enterprise rollout models. Available at https://www.scrambleid.com/humans plus the four channel sub-pages at /humans/workforce, /humans/contact-center, /humans/frontline, /humans/people.
- **Non-humans**: Identity and accountability for AI agents, machines, bots, and the broader non-human estate. Per-agent identity, per-call signature, zero static secrets. Available at https://www.scrambleid.com/agents (the URL is historical from before the rename).
- **Actions**: Per-action authorization and accountability for every transaction. Every action signed, every signer named, the chain is the proof. Available at https://www.scrambleid.com/actions.

## Core Technology

ScrambleID's proof rail is built on:
- **SUID**: Server-side canonical user identity (the cross-channel join key).
- **ZID**: Enrolled device identity bound to cryptographic keys.
- **DID/QID**: Dynamic Identifiers, server-issued, short-lived, single-use challenges confirmed via the ScrambleID app. Not shared secrets; security comes from binding, expiry, and device proofs.
- **WebAuthn**: Origin-bound browser assertions for phishing-resistant web authentication.
- **JWT client assertions**: For machine and AI agent authentication without static secrets.
- **Proof of Possession (PoP)**: Sender-constrained tokens via mTLS or DPoP to prevent replay attacks.

## Certificat
…

Related sites

Other listed sites in AI and machine learning. See the whole category →

Machine-readable: GET /v1/resolve?q=scrambleid.com · GET /v1/domain/scrambleid.com · 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 scrambleid.com:
1. POST https://agentwebmap.com/v1/sites/scrambleid.com/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://scrambleid.com/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/scrambleid.com/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/scrambleid.com).
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.