{
  "$schema": "https://schema.org",
  "generatedFrom": "src/content/{site,pages,faqs}.ts",
  "organization": {
    "@id": "https://ambridge.io/#organization",
    "name": "Ambridge",
    "legalName": "Ambridge Technologies",
    "url": "https://ambridge.io/",
    "description": "Ambridge is digital trust infrastructure: APIs for document signing, institutional attestation, document verification and identity (KYC & Video KYC).",
    "positioning": "Ambridge provides identity, document signing, attestation, verification and digital trust infrastructure as a platform.",
    "category": "Trust & Identity Infrastructure",
    "sameAs": []
  },
  "website": {
    "@id": "https://ambridge.io/#website",
    "url": "https://ambridge.io/",
    "inLanguage": "en"
  },
  "platform": {
    "@id": "https://ambridge.io/#platform",
    "name": "Ambridge Platform",
    "conceptualModel": "Identity, document signing, attestation, verification and digital trust delivered as API infrastructure.",
    "hierarchy": [
      "Digital trust infrastructure",
      "Digital identity",
      "Document signing",
      "Document attestation",
      "Document verification",
      "Security & compliance",
      "Developer / API integration"
    ]
  },
  "services": [
    {
      "@id": "https://ambridge.io/#service-sign",
      "slug": "sign",
      "name": "Ambridge Sign",
      "summary": "Digital signing infrastructure for agreements that need to be signed, trusted and verified.",
      "url": "https://ambridge.io/products/digital-signature"
    },
    {
      "@id": "https://ambridge.io/#service-attest",
      "slug": "attest",
      "name": "Ambridge Attest",
      "summary": "Institutional document attestation and independent verification.",
      "url": "https://ambridge.io/products/document-attestation"
    },
    {
      "@id": "https://ambridge.io/#service-identity",
      "slug": "identity",
      "name": "Ambridge Identity",
      "summary": "KYC, Video KYC and identity verification infrastructure.",
      "url": "https://ambridge.io/products/identity-verification"
    }
  ],
  "terminology": {
    "digital trust infrastructure": "Shared machinery — identity, signatures, attestation, verification and evidence — consumed as an API instead of rebuilt per application.",
    "document signing": "Capturing a signer's intent and binding it to a document with evidence about who signed and when.",
    "document attestation": "An institution formally standing behind a document it issues so recipients can confirm provenance.",
    "document verification": "Confirming a presented document is unaltered and came from the claimed issuer or signer.",
    "identity verification": "Establishing remotely that a person is who they claim to be, via document checks, face match and liveness.",
    "Video KYC": "A live, recorded video session in which an agent verifies identity documents and presence in real time."
  },
  "pages": [
    {
      "path": "/",
      "canonical": "https://ambridge.io/",
      "title": "Ambridge — Digital Trust, Signing, Attestation & Identity Infrastructure",
      "description": "Ambridge is API-first digital trust infrastructure: sign documents, attest records you issue, verify documents presented to you and verify identities with KYC and Video KYC.",
      "h1": "Sign documents. Attest records. Verify identities.",
      "schemaType": "WebPage",
      "entity": "https://ambridge.io/#organization",
      "indexable": true,
      "breadcrumbs": [],
      "relatedPages": [
        "https://ambridge.io/products/digital-signature",
        "https://ambridge.io/products/document-attestation",
        "https://ambridge.io/products/identity-verification",
        "https://ambridge.io/developers/api-documentation",
        "https://ambridge.io/trust-center"
      ],
      "ai": {
        "summary": "Home page of Ambridge, a platform company providing digital trust infrastructure: document signing, institutional document attestation, document verification and identity verification, delivered through APIs.",
        "entityType": "Organization",
        "primaryTopic": "Digital trust infrastructure",
        "secondaryTopics": [
          "Document signing",
          "Document attestation",
          "Document verification",
          "Digital identity"
        ],
        "audience": [
          "Businesses",
          "Regulated institutions",
          "Developers",
          "Platforms"
        ],
        "keyCapabilities": [
          "Digital and identity-verified document signing",
          "Institutional document attestation",
          "Independent document verification",
          "KYC and Video KYC identity verification"
        ],
        "primaryUseCases": [
          "Customer onboarding",
          "Agreement execution",
          "Credential issuance and checking"
        ],
        "relatedServices": [
          "sign",
          "attest",
          "identity"
        ]
      },
      "faqs": [
        "platform-001",
        "platform-002",
        "platform-003",
        "platform-004",
        "trust-001",
        "trust-002"
      ]
    },
    {
      "path": "/products/digital-signature",
      "canonical": "https://ambridge.io/products/digital-signature",
      "title": "Digital Document Signing Infrastructure | Ambridge Sign",
      "description": "Ambridge Sign is API-first document signing with tiered assurance, identity-verified signers and a tamper-evident Signing Log you can hand to an auditor.",
      "h1": "Digital signing infrastructure for agreements that need to be signed, trusted and verified",
      "schemaType": "Service",
      "entity": "https://ambridge.io/#service-sign",
      "indexable": true,
      "breadcrumbs": [],
      "relatedPages": [
        "https://ambridge.io/products/identity-verification",
        "https://ambridge.io/products/document-attestation",
        "https://ambridge.io/developers/api-documentation",
        "https://ambridge.io/pricing",
        "https://ambridge.io/security"
      ],
      "ai": {
        "summary": "Service page for Ambridge Sign, Ambridge's digital document signing service. Explains assurance levels, the evidence trail (Signing Log), use cases and API integration.",
        "entityType": "Service",
        "primaryTopic": "Digital document signing",
        "secondaryTopics": [
          "Electronic signatures",
          "Signer authentication",
          "Audit evidence"
        ],
        "audience": [
          "Businesses",
          "Regulated institutions",
          "Developers"
        ],
        "keyCapabilities": [
          "Tiered assurance levels",
          "Identity-verified signing",
          "Tamper-evident Signing Log",
          "Signatures API and webhooks"
        ],
        "primaryUseCases": [
          "Contract execution",
          "Customer agreements",
          "High-volume institutional signing"
        ],
        "relatedServices": [
          "identity",
          "attest"
        ]
      },
      "faqs": [
        "signing-001",
        "signing-002",
        "signing-003",
        "signing-004",
        "signing-005",
        "attest-003",
        "identity-004"
      ]
    },
    {
      "path": "/products/document-attestation",
      "canonical": "https://ambridge.io/products/document-attestation",
      "title": "Document Attestation & Verification Platform | Ambridge Attest",
      "description": "Ambridge Attest lets institutions attest the documents they issue and gives any third party a way to verify issuer, integrity and validity in seconds.",
      "h1": "Document attestation: issue documents anyone can verify",
      "schemaType": "Service",
      "entity": "https://ambridge.io/#service-attest",
      "indexable": true,
      "breadcrumbs": [],
      "relatedPages": [
        "https://ambridge.io/products/digital-signature",
        "https://ambridge.io/products/identity-verification",
        "https://ambridge.io/developers/api-documentation",
        "https://ambridge.io/solutions/education"
      ],
      "ai": {
        "summary": "Service page for Ambridge Attest, covering how institutions issue attested documents, how each document receives a verification identity, and how third parties verify issuer and integrity.",
        "entityType": "Service",
        "primaryTopic": "Document attestation and verification",
        "secondaryTopics": [
          "Credential verification",
          "Document provenance",
          "QR verification"
        ],
        "audience": [
          "Universities",
          "Professional bodies",
          "Employers",
          "Government agencies"
        ],
        "keyCapabilities": [
          "Attestation of issued documents",
          "Unique document verification identity",
          "Public verification by ID, PIN or QR",
          "Attestations and Verification APIs"
        ],
        "primaryUseCases": [
          "Degree and transcript verification",
          "Licence and membership checks",
          "Employment and financial letters"
        ],
        "relatedServices": [
          "sign",
          "identity"
        ]
      },
      "faqs": [
        "attest-001",
        "attest-002",
        "attest-003",
        "attest-004",
        "verify-001",
        "verify-002",
        "verify-003"
      ]
    },
    {
      "path": "/products/identity-verification",
      "canonical": "https://ambridge.io/products/identity-verification",
      "title": "Identity Verification, KYC & Video KYC Infrastructure | Ambridge Identity",
      "description": "Ambridge Identity provides KYC, Video KYC, document checks, face match and liveness as infrastructure — with audit trails that attach to signing and attestation workflows.",
      "h1": "Identity verification infrastructure for the digital world",
      "schemaType": "Service",
      "entity": "https://ambridge.io/#service-identity",
      "indexable": true,
      "breadcrumbs": [],
      "relatedPages": [
        "https://ambridge.io/products/digital-signature",
        "https://ambridge.io/products/document-attestation",
        "https://ambridge.io/developers/api-documentation",
        "https://ambridge.io/solutions/financial-services"
      ],
      "ai": {
        "summary": "Service page for Ambridge Identity, covering KYC, Video KYC, identity document checks, face match and liveness, and how identity evidence is attached to signing workflows.",
        "entityType": "Service",
        "primaryTopic": "Digital identity verification",
        "secondaryTopics": [
          "KYC",
          "Video KYC",
          "Liveness detection",
          "Onboarding"
        ],
        "audience": [
          "Financial services",
          "Regulated institutions",
          "Developers"
        ],
        "keyCapabilities": [
          "Identity document verification",
          "Face match and liveness",
          "Assisted Video KYC sessions",
          "Identity API with audit trails"
        ],
        "primaryUseCases": [
          "Customer onboarding",
          "Identity-verified signing",
          "Regulated KYC programmes"
        ],
        "relatedServices": [
          "sign",
          "attest"
        ]
      },
      "faqs": [
        "identity-001",
        "identity-002",
        "identity-003",
        "identity-004",
        "security-004"
      ]
    },
    {
      "path": "/developers/api-documentation",
      "canonical": "https://ambridge.io/developers/api-documentation",
      "title": "Ambridge APIs for Signing, Attestation, Verification & Identity",
      "description": "One API surface for signing, attestation, verification and identity — typed SDKs, idempotent endpoints, signed webhooks and a sandbox that behaves like production.",
      "h1": "One API surface for signing, attestation and identity",
      "schemaType": "WebPage",
      "entity": "https://ambridge.io/#organization",
      "indexable": true,
      "breadcrumbs": [],
      "relatedPages": [
        "https://ambridge.io/products/digital-signature",
        "https://ambridge.io/products/document-attestation",
        "https://ambridge.io/products/identity-verification",
        "https://ambridge.io/pricing"
      ],
      "ai": {
        "summary": "Developer documentation overview describing the Signatures, Attestations, Verification and Identity APIs, SDKs, webhooks and sandbox environment.",
        "entityType": "WebPage",
        "primaryTopic": "Developer platform and APIs",
        "secondaryTopics": [
          "REST API",
          "SDKs",
          "Webhooks",
          "Sandbox"
        ],
        "audience": [
          "Developers",
          "Technical architects",
          "Platform teams"
        ],
        "keyCapabilities": [
          "Signatures API",
          "Attestations API",
          "Verification API",
          "Identity API"
        ],
        "relatedServices": [
          "sign",
          "attest",
          "identity"
        ]
      },
      "faqs": [
        "signing-004",
        "verify-002",
        "dev-001",
        "dev-002",
        "dev-003",
        "pricing-002"
      ]
    },
    {
      "path": "/pricing",
      "canonical": "https://ambridge.io/pricing",
      "title": "Ambridge Pricing — Sign, Attest and Identity Plans",
      "description": "Usage-based pricing for Ambridge Sign and Ambridge Attest, with Ambridge Identity quoted per programme based on jurisdiction, check types and volume.",
      "h1": "Pricing for signing, attestation and identity",
      "schemaType": "WebPage",
      "entity": "https://ambridge.io/#organization",
      "indexable": true,
      "breadcrumbs": [],
      "relatedPages": [
        "https://ambridge.io/products/digital-signature",
        "https://ambridge.io/products/document-attestation",
        "https://ambridge.io/products/identity-verification",
        "https://ambridge.io/contact-sales"
      ],
      "ai": {
        "summary": "Pricing page listing plans for the Ambridge Sign and Ambridge Attest services and explaining that Ambridge Identity is quoted individually.",
        "entityType": "WebPage",
        "primaryTopic": "Pricing",
        "secondaryTopics": [
          "Plans",
          "Usage-based billing"
        ],
        "audience": [
          "Businesses",
          "Procurement",
          "Developers"
        ],
        "relatedServices": [
          "sign",
          "attest",
          "identity"
        ]
      },
      "faqs": [
        "platform-005",
        "pricing-001",
        "pricing-002"
      ]
    },
    {
      "path": "/compare/docusign-alternative",
      "canonical": "https://ambridge.io/compare/docusign-alternative",
      "title": "Ambridge vs Other Signing & Verification Platforms — Comparison",
      "description": "Compare Ambridge with other document signing and verification platforms on regional data residency, evidence, attestation and identity capabilities.",
      "h1": "How Ambridge compares on signing, attestation and identity",
      "schemaType": "WebPage",
      "entity": "https://ambridge.io/#organization",
      "indexable": true,
      "breadcrumbs": [],
      "relatedPages": [
        "https://ambridge.io/products/digital-signature",
        "https://ambridge.io/products/document-attestation",
        "https://ambridge.io/security/data-centers"
      ],
      "ai": {
        "summary": "Comparison page setting Ambridge's signing, attestation, identity and data-residency capabilities against other platforms in the same category.",
        "entityType": "WebPage",
        "primaryTopic": "Platform comparison",
        "secondaryTopics": [
          "Data residency",
          "Feature comparison"
        ],
        "audience": [
          "Buyers",
          "Procurement",
          "Technical evaluators"
        ],
        "relatedServices": [
          "sign",
          "attest",
          "identity"
        ]
      },
      "faqs": []
    },
    {
      "path": "/trust-center",
      "canonical": "https://ambridge.io/trust-center",
      "title": "Ambridge Trust Center — Digital Trust, Evidence and Controls",
      "description": "How Ambridge builds digital trust: tamper-evident documents, encryption, least-privilege access, regional processing and evidence designed for auditors.",
      "h1": "Digital trust infrastructure and the evidence behind it",
      "schemaType": "WebPage",
      "entity": "https://ambridge.io/#organization",
      "indexable": true,
      "breadcrumbs": [],
      "relatedPages": [
        "https://ambridge.io/security",
        "https://ambridge.io/products/digital-signature",
        "https://ambridge.io/products/document-attestation",
        "https://ambridge.io/products/identity-verification"
      ],
      "ai": {
        "summary": "Trust centre explaining what digital trust infrastructure means at Ambridge, the commitments behind it and the evidence produced by signing, attestation and identity.",
        "entityType": "WebPage",
        "primaryTopic": "Digital trust infrastructure",
        "secondaryTopics": [
          "Audit evidence",
          "Data residency",
          "Encryption"
        ],
        "audience": [
          "Risk teams",
          "Compliance teams",
          "Buyers"
        ],
        "relatedServices": [
          "sign",
          "attest",
          "identity"
        ]
      },
      "faqs": [
        "platform-004",
        "trust-001",
        "trust-002",
        "trust-003",
        "security-001"
      ]
    },
    {
      "path": "/contact-sales",
      "canonical": "https://ambridge.io/contact-sales",
      "title": "Contact Ambridge — Talk to the Trust Infrastructure Team",
      "description": "Contact the Ambridge team about document signing, attestation, verification or identity, request a demo or get a quote for a KYC programme.",
      "h1": "Talk to the Ambridge team",
      "schemaType": "ContactPage",
      "entity": "https://ambridge.io/#organization",
      "indexable": true,
      "breadcrumbs": [],
      "relatedPages": [
        "https://ambridge.io/pricing",
        "https://ambridge.io/developers/api-documentation"
      ],
      "ai": {
        "summary": "Contact page for reaching the Ambridge sales and support teams about signing, attestation, verification and identity.",
        "entityType": "ContactPage",
        "primaryTopic": "Contact",
        "secondaryTopics": [
          "Demo request",
          "Sales enquiry"
        ],
        "audience": [
          "Prospective customers",
          "Partners"
        ]
      },
      "faqs": []
    },
    {
      "path": "/faq",
      "canonical": "https://ambridge.io/faq",
      "title": "Ambridge FAQ — Signing, Attestation, Identity & Verification Answered",
      "description": "Answers to common questions about Ambridge: what the platform does, how signing, attestation, verification and identity work, developer integration, security and pricing.",
      "h1": "Frequently asked questions about Ambridge",
      "schemaType": "FAQPage",
      "entity": "https://ambridge.io/#organization",
      "indexable": true,
      "breadcrumbs": [],
      "relatedPages": [
        "https://ambridge.io/",
        "https://ambridge.io/products/digital-signature",
        "https://ambridge.io/products/document-attestation",
        "https://ambridge.io/products/identity-verification",
        "https://ambridge.io/security"
      ],
      "ai": {
        "summary": "Knowledge base answering the most common questions about Ambridge, its platform, its three services, developer integration, security and compliance, and pricing.",
        "entityType": "FAQPage",
        "primaryTopic": "Ambridge frequently asked questions",
        "secondaryTopics": [
          "Signing",
          "Attestation",
          "Identity",
          "Verification",
          "Security"
        ],
        "audience": [
          "Prospective customers",
          "Developers",
          "Researchers",
          "AI agents"
        ],
        "relatedServices": [
          "sign",
          "attest",
          "identity"
        ]
      },
      "faqs": [
        "platform-001",
        "platform-002",
        "platform-003",
        "platform-004",
        "platform-005",
        "signing-001",
        "signing-002",
        "signing-003",
        "signing-004",
        "signing-005",
        "attest-001",
        "attest-002",
        "attest-003",
        "attest-004",
        "verify-001",
        "verify-002",
        "verify-003",
        "identity-001",
        "identity-002",
        "identity-003",
        "identity-004",
        "trust-001",
        "trust-002",
        "trust-003",
        "dev-001",
        "dev-002",
        "dev-003",
        "security-001",
        "security-002",
        "security-003",
        "security-004",
        "security-005",
        "security-006",
        "pricing-001",
        "pricing-002"
      ]
    },
    {
      "path": "/security",
      "canonical": "https://ambridge.io/security",
      "title": "Security at Ambridge — Protecting Documents and Identity Data",
      "description": "How Ambridge secures documents and identity data: encryption in transit and at rest, least-privilege access, audit logging, testing and compliance programmes.",
      "h1": "Security for documents, signatures and identity data",
      "schemaType": "WebPage",
      "entity": "https://ambridge.io/#organization",
      "indexable": true,
      "breadcrumbs": [
        {
          "name": "Home",
          "url": "https://ambridge.io/"
        },
        {
          "name": "Security & compliance",
          "url": "https://ambridge.io/security"
        }
      ],
      "relatedPages": [
        "https://ambridge.io/security/soc-2",
        "https://ambridge.io/security/iso-27001",
        "https://ambridge.io/security/gdpr",
        "https://ambridge.io/security/data-centers",
        "https://ambridge.io/trust-center"
      ],
      "ai": {
        "summary": "Security overview describing the technical and organisational controls protecting Ambridge documents, signatures and identity data.",
        "entityType": "WebPage",
        "primaryTopic": "Information security",
        "secondaryTopics": [
          "Encryption",
          "Access control",
          "Audit logging",
          "Compliance"
        ],
        "audience": [
          "Security teams",
          "Compliance teams",
          "Buyers"
        ],
        "relatedServices": [
          "sign",
          "attest",
          "identity"
        ]
      },
      "faqs": [
        "security-001",
        "security-002",
        "security-003",
        "security-004",
        "security-005"
      ]
    },
    {
      "path": "/security/soc-2",
      "canonical": "https://ambridge.io/security/soc-2",
      "title": "SOC 2 | Ambridge Security & Compliance",
      "description": "How Ambridge meets the SOC 2 trust service principles — security, availability, processing integrity, confidentiality and privacy — and how reports are requested.",
      "h1": "SOC 2 compliance",
      "schemaType": "WebPage",
      "entity": "https://ambridge.io/#organization",
      "indexable": true,
      "breadcrumbs": [
        {
          "name": "Home",
          "url": "https://ambridge.io/"
        },
        {
          "name": "Security & compliance",
          "url": "https://ambridge.io/security"
        },
        {
          "name": "SOC 2",
          "url": "https://ambridge.io/security/soc-2"
        }
      ],
      "relatedPages": [
        "https://ambridge.io/security",
        "https://ambridge.io/security/iso-27001",
        "https://ambridge.io/trust-center"
      ],
      "ai": {
        "summary": "Compliance page describing Ambridge's SOC 2 programme, the five trust service principles and the certification process.",
        "entityType": "WebPage",
        "primaryTopic": "SOC 2 compliance",
        "secondaryTopics": [
          "Trust service principles",
          "Independent audit"
        ],
        "audience": [
          "Security teams",
          "Compliance teams",
          "Procurement"
        ]
      },
      "faqs": [
        "security-002"
      ]
    },
    {
      "path": "/security/iso-27001",
      "canonical": "https://ambridge.io/security/iso-27001",
      "title": "ISO 27001 | Ambridge Security & Compliance",
      "description": "Ambridge's information security management system aligned to ISO/IEC 27001: risk assessment, documented controls, internal audit and management review.",
      "h1": "ISO 27001 compliance",
      "schemaType": "WebPage",
      "entity": "https://ambridge.io/#organization",
      "indexable": true,
      "breadcrumbs": [
        {
          "name": "Home",
          "url": "https://ambridge.io/"
        },
        {
          "name": "Security & compliance",
          "url": "https://ambridge.io/security"
        },
        {
          "name": "ISO 27001",
          "url": "https://ambridge.io/security/iso-27001"
        }
      ],
      "relatedPages": [
        "https://ambridge.io/security",
        "https://ambridge.io/security/soc-2",
        "https://ambridge.io/trust-center"
      ],
      "ai": {
        "summary": "Compliance page describing how Ambridge aligns its information security management system to ISO/IEC 27001.",
        "entityType": "WebPage",
        "primaryTopic": "ISO 27001",
        "secondaryTopics": [
          "ISMS",
          "Risk management",
          "Security controls"
        ],
        "audience": [
          "Security teams",
          "Compliance teams",
          "Procurement"
        ]
      },
      "faqs": [
        "security-003"
      ]
    },
    {
      "path": "/security/gdpr",
      "canonical": "https://ambridge.io/security/gdpr",
      "title": "GDPR | Ambridge Data Protection & Privacy Compliance",
      "description": "How Ambridge supports GDPR obligations: processing terms, EU data residency, retention, sub-processors and handling of data subject requests.",
      "h1": "GDPR compliance",
      "schemaType": "WebPage",
      "entity": "https://ambridge.io/#organization",
      "indexable": true,
      "breadcrumbs": [
        {
          "name": "Home",
          "url": "https://ambridge.io/"
        },
        {
          "name": "Security & compliance",
          "url": "https://ambridge.io/security"
        },
        {
          "name": "GDPR",
          "url": "https://ambridge.io/security/gdpr"
        }
      ],
      "relatedPages": [
        "https://ambridge.io/security",
        "https://ambridge.io/privacy-policy",
        "https://ambridge.io/security/data-centers"
      ],
      "ai": {
        "summary": "Data protection page describing Ambridge's GDPR posture, including residency, retention, sub-processors and data subject rights.",
        "entityType": "WebPage",
        "primaryTopic": "GDPR compliance",
        "secondaryTopics": [
          "Data protection",
          "Data residency",
          "Data subject rights"
        ],
        "audience": [
          "Privacy teams",
          "Legal teams",
          "Compliance teams"
        ]
      },
      "faqs": [
        "security-006"
      ]
    },
    {
      "path": "/security/data-centers",
      "canonical": "https://ambridge.io/security/data-centers",
      "title": "Data Centre Locations & Compliance Matrix | Ambridge",
      "description": "Ambridge data centre regions and the compliance standards each location is covered by, so regulated customers can choose where documents and identity data are processed.",
      "h1": "Data center & security compliance matrix",
      "schemaType": "WebPage",
      "entity": "https://ambridge.io/#organization",
      "indexable": true,
      "breadcrumbs": [
        {
          "name": "Home",
          "url": "https://ambridge.io/"
        },
        {
          "name": "Security & compliance",
          "url": "https://ambridge.io/security"
        },
        {
          "name": "Data centres",
          "url": "https://ambridge.io/security/data-centers"
        }
      ],
      "relatedPages": [
        "https://ambridge.io/security",
        "https://ambridge.io/security/gdpr",
        "https://ambridge.io/compare/docusign-alternative"
      ],
      "ai": {
        "summary": "Reference page listing Ambridge data centre locations and the compliance standards applicable to each region.",
        "entityType": "WebPage",
        "primaryTopic": "Data residency and data centre compliance",
        "secondaryTopics": [
          "Regional processing",
          "Compliance standards"
        ],
        "audience": [
          "Compliance teams",
          "Security teams",
          "Regulated institutions"
        ]
      },
      "faqs": [
        "security-005"
      ]
    },
    {
      "path": "/privacy-policy",
      "canonical": "https://ambridge.io/privacy-policy",
      "title": "Privacy Policy | Ambridge",
      "description": "How Ambridge collects, uses, shares and retains personal information across its signing, attestation, verification and identity services.",
      "h1": "Privacy Policy",
      "schemaType": "WebPage",
      "entity": "https://ambridge.io/#organization",
      "indexable": true,
      "breadcrumbs": [
        {
          "name": "Home",
          "url": "https://ambridge.io/"
        },
        {
          "name": "Privacy Policy",
          "url": "https://ambridge.io/privacy-policy"
        }
      ],
      "relatedPages": [
        "https://ambridge.io/terms-of-service",
        "https://ambridge.io/security/gdpr"
      ],
      "ai": {
        "summary": "Legal page setting out the Ambridge privacy policy.",
        "entityType": "WebPage",
        "primaryTopic": "Privacy policy",
        "secondaryTopics": [
          "Personal data",
          "Retention"
        ],
        "audience": [
          "Customers",
          "End users",
          "Legal teams"
        ]
      },
      "faqs": []
    },
    {
      "path": "/terms-of-service",
      "canonical": "https://ambridge.io/terms-of-service",
      "title": "Terms of Service | Ambridge",
      "description": "The terms governing use of the Ambridge platform, including the Sign, Attest and Identity services.",
      "h1": "Terms of Service",
      "schemaType": "WebPage",
      "entity": "https://ambridge.io/#organization",
      "indexable": true,
      "breadcrumbs": [
        {
          "name": "Home",
          "url": "https://ambridge.io/"
        },
        {
          "name": "Terms of Service",
          "url": "https://ambridge.io/terms-of-service"
        }
      ],
      "relatedPages": [
        "https://ambridge.io/privacy-policy"
      ],
      "ai": {
        "summary": "Legal page setting out the Ambridge terms of service.",
        "entityType": "WebPage",
        "primaryTopic": "Terms of service",
        "secondaryTopics": [
          "Contractual terms"
        ],
        "audience": [
          "Customers",
          "Legal teams"
        ]
      },
      "faqs": []
    },
    {
      "path": "/solutions/financial-services",
      "canonical": "https://ambridge.io/solutions/financial-services",
      "title": "Digital Trust for Financial Services | Ambridge",
      "description": "Onboard customers with KYC and Video KYC, execute agreements with identity-verified signing and verify documents — with regional data residency for regulated institutions.",
      "h1": "Onboard customers and close agreements without leaving the regulator behind",
      "schemaType": "WebPage",
      "entity": "https://ambridge.io/#organization",
      "indexable": true,
      "breadcrumbs": [
        {
          "name": "Home",
          "url": "https://ambridge.io/"
        },
        {
          "name": "Solutions",
          "url": "https://ambridge.io/solutions"
        },
        {
          "name": "Financial services",
          "url": "https://ambridge.io/solutions/financial-services"
        }
      ],
      "relatedPages": [
        "https://ambridge.io/products/identity-verification",
        "https://ambridge.io/products/digital-signature",
        "https://ambridge.io/security"
      ],
      "ai": {
        "summary": "Industry page describing how banks, lenders and financial institutions use Ambridge for onboarding, KYC and agreement execution.",
        "entityType": "WebPage",
        "primaryTopic": "Digital trust for financial services",
        "secondaryTopics": [
          "KYC",
          "Onboarding",
          "Agreements"
        ],
        "audience": [
          "Banks",
          "Lenders",
          "Fintechs"
        ],
        "relatedServices": [
          "identity",
          "sign"
        ]
      },
      "faqs": []
    },
    {
      "path": "/solutions/government",
      "canonical": "https://ambridge.io/solutions/government",
      "title": "Digital Trust for Government & Public Sector | Ambridge",
      "description": "Sovereign, in-region processing for public sector signing, citizen identity verification and verifiable documents issued by government bodies.",
      "h1": "Sovereign signing and verification for public institutions",
      "schemaType": "WebPage",
      "entity": "https://ambridge.io/#organization",
      "indexable": true,
      "breadcrumbs": [
        {
          "name": "Home",
          "url": "https://ambridge.io/"
        },
        {
          "name": "Solutions",
          "url": "https://ambridge.io/solutions"
        },
        {
          "name": "Government",
          "url": "https://ambridge.io/solutions/government"
        }
      ],
      "relatedPages": [
        "https://ambridge.io/products/document-attestation",
        "https://ambridge.io/products/identity-verification",
        "https://ambridge.io/security/data-centers"
      ],
      "ai": {
        "summary": "Industry page describing public sector use of Ambridge for in-region signing, identity verification and verifiable documents.",
        "entityType": "WebPage",
        "primaryTopic": "Digital trust for government",
        "secondaryTopics": [
          "Data sovereignty",
          "Citizen identity",
          "Verifiable documents"
        ],
        "audience": [
          "Government agencies",
          "Public sector bodies"
        ],
        "relatedServices": [
          "attest",
          "identity",
          "sign"
        ]
      },
      "faqs": []
    },
    {
      "path": "/solutions/education",
      "canonical": "https://ambridge.io/solutions/education",
      "title": "Degree & Transcript Attestation for Education | Ambridge",
      "description": "Universities and examination bodies attest degrees and transcripts with Ambridge so employers and authorities can verify them instantly.",
      "h1": "Issue degrees and transcripts that anyone can verify instantly",
      "schemaType": "WebPage",
      "entity": "https://ambridge.io/#organization",
      "indexable": true,
      "breadcrumbs": [
        {
          "name": "Home",
          "url": "https://ambridge.io/"
        },
        {
          "name": "Solutions",
          "url": "https://ambridge.io/solutions"
        },
        {
          "name": "Education",
          "url": "https://ambridge.io/solutions/education"
        }
      ],
      "relatedPages": [
        "https://ambridge.io/products/document-attestation",
        "https://ambridge.io/products/digital-signature"
      ],
      "ai": {
        "summary": "Industry page describing how universities and awarding bodies use Ambridge Attest for degree and transcript verification.",
        "entityType": "WebPage",
        "primaryTopic": "Credential attestation for education",
        "secondaryTopics": [
          "Degrees",
          "Transcripts",
          "Credential verification"
        ],
        "audience": [
          "Universities",
          "Examination bodies",
          "Employers"
        ],
        "relatedServices": [
          "attest"
        ]
      },
      "faqs": []
    },
    {
      "path": "/solutions/healthcare",
      "canonical": "https://ambridge.io/solutions/healthcare",
      "title": "Verified Consent & Signing for Healthcare | Ambridge",
      "description": "Capture patient consent with verified identity, sign clinical and administrative documents and keep an audit trail suited to regulated healthcare workflows.",
      "h1": "Consent and clinical documentation with verified identity",
      "schemaType": "WebPage",
      "entity": "https://ambridge.io/#organization",
      "indexable": true,
      "breadcrumbs": [
        {
          "name": "Home",
          "url": "https://ambridge.io/"
        },
        {
          "name": "Solutions",
          "url": "https://ambridge.io/solutions"
        },
        {
          "name": "Healthcare",
          "url": "https://ambridge.io/solutions/healthcare"
        }
      ],
      "relatedPages": [
        "https://ambridge.io/products/digital-signature",
        "https://ambridge.io/products/identity-verification",
        "https://ambridge.io/security"
      ],
      "ai": {
        "summary": "Industry page describing healthcare use of Ambridge for identity-verified consent and document signing.",
        "entityType": "WebPage",
        "primaryTopic": "Digital trust for healthcare",
        "secondaryTopics": [
          "Patient consent",
          "Identity-verified signing"
        ],
        "audience": [
          "Healthcare providers",
          "Health platforms"
        ],
        "relatedServices": [
          "sign",
          "identity"
        ]
      },
      "faqs": []
    },
    {
      "path": "/sitemap",
      "canonical": "https://ambridge.io/sitemap",
      "title": "Sitemap — Every Ambridge Page in One Place",
      "description": "Browse every Ambridge page: signing, attestation and identity services, developer resources, pricing, comparison, security and compliance, and legal policies.",
      "h1": "Sitemap",
      "schemaType": "WebPage",
      "entity": "https://ambridge.io/#organization",
      "indexable": true,
      "breadcrumbs": [
        {
          "name": "Home",
          "url": "https://ambridge.io/"
        },
        {
          "name": "Sitemap",
          "url": "https://ambridge.io/sitemap"
        }
      ],
      "relatedPages": [],
      "ai": {
        "summary": "Human-readable index of every public Ambridge page, grouped by platform services, resources, security and compliance, and legal documents.",
        "entityType": "WebPage",
        "primaryTopic": "Site index",
        "secondaryTopics": [
          "Navigation",
          "Page directory"
        ],
        "audience": [
          "Visitors",
          "Search engines",
          "AI agents"
        ]
      },
      "faqs": []
    }
  ],
  "faqCategories": [
    {
      "id": "platform",
      "title": "About Ambridge",
      "description": "What Ambridge is, who it is for and how the platform fits together."
    },
    {
      "id": "signing",
      "title": "Document signing",
      "description": "Electronic and certified signing, assurance levels and evidence."
    },
    {
      "id": "attestation",
      "title": "Document attestation",
      "description": "Issuing attested documents and proving they came from you."
    },
    {
      "id": "identity",
      "title": "Identity & KYC",
      "description": "KYC, Video KYC and identity verification."
    },
    {
      "id": "verification",
      "title": "Verification",
      "description": "How signed and attested documents are checked by third parties."
    },
    {
      "id": "trust",
      "title": "Digital trust infrastructure",
      "description": "What trust infrastructure means and how the services combine."
    },
    {
      "id": "developers",
      "title": "Developers & APIs",
      "description": "Integration, SDKs, webhooks and sandbox."
    },
    {
      "id": "security",
      "title": "Security & compliance",
      "description": "Controls, certifications, data protection and residency."
    },
    {
      "id": "pricing",
      "title": "Pricing",
      "description": "How Ambridge is priced across the three services."
    }
  ],
  "faqs": [
    {
      "id": "platform-001",
      "question": "What is Ambridge?",
      "answer": "Ambridge is digital trust infrastructure delivered as a platform. It provides APIs and workflows for signing documents, attesting documents you issue, verifying documents presented to you, and verifying the identity of the people involved — under one account, one API surface and one evidence model.",
      "category": "platform",
      "urls": [
        "https://ambridge.io/",
        "https://ambridge.io/faq"
      ]
    },
    {
      "id": "platform-002",
      "question": "What does Ambridge do?",
      "answer": "Ambridge runs three connected services: Sign for digital signing, Attest for institutional document attestation and verification, and Identity for KYC, Video KYC and identity verification. Each can be used on its own or combined, so a single workflow can verify a person, have them sign, and produce a document a third party can independently verify.",
      "category": "platform",
      "urls": [
        "https://ambridge.io/",
        "https://ambridge.io/faq"
      ]
    },
    {
      "id": "platform-003",
      "question": "Who is Ambridge for?",
      "answer": "Ambridge is built for organisations whose documents and onboarding carry legal or regulatory weight: financial services, government and public sector, education, healthcare, and the platforms and developers that serve them.",
      "category": "platform",
      "urls": [
        "https://ambridge.io/",
        "https://ambridge.io/faq"
      ]
    },
    {
      "id": "platform-004",
      "question": "How do signing, attestation, identity and verification relate to each other?",
      "answer": "Identity establishes who a party is. Signing captures their intent on a document and records the evidence. Attestation lets an institution stand behind a document it issues. Verification lets anyone later confirm that a document is intact and came from the claimed issuer or signer. Together they form a chain of trust from person to document to independent check.",
      "category": "trust",
      "urls": [
        "https://ambridge.io/",
        "https://ambridge.io/faq",
        "https://ambridge.io/trust-center"
      ]
    },
    {
      "id": "platform-005",
      "question": "Do I have to adopt the whole platform at once?",
      "answer": "No. Sign, Attest and Identity are independently usable services with their own APIs and pricing. Most teams start with one service and add the others when the workflow needs them.",
      "category": "platform",
      "urls": [
        "https://ambridge.io/faq",
        "https://ambridge.io/pricing"
      ]
    },
    {
      "id": "signing-001",
      "question": "What is digital document signing?",
      "answer": "Digital document signing is the process of capturing a signer's intent electronically and binding it to a specific document, together with the evidence needed to show who signed, what they saw and when. The result is a document whose integrity can be checked afterwards rather than a scanned image of a handwriting.",
      "category": "signing",
      "urls": [
        "https://ambridge.io/products/digital-signature",
        "https://ambridge.io/faq"
      ]
    },
    {
      "id": "signing-002",
      "question": "How does Ambridge Sign work?",
      "answer": "You create a signing request through the API or dashboard, choose an assurance level, and Ambridge handles delivery, signer authentication, capture of intent and sealing of the finished document. Every request produces a Signing Log — a tamper-evident audit record covering the document, the signers and the events in the session.",
      "category": "signing",
      "urls": [
        "https://ambridge.io/products/digital-signature",
        "https://ambridge.io/faq"
      ]
    },
    {
      "id": "signing-003",
      "question": "What assurance levels does Ambridge Sign offer?",
      "answer": "Sign supports tiered assurance, from a straightforward electronic signature, to certified signing with stronger signer authentication, to ID-verified signing where the signer's identity is checked with Ambridge Identity before they can sign. You choose the level per request, so low-risk and high-risk documents can share one integration.",
      "category": "signing",
      "urls": [
        "https://ambridge.io/products/digital-signature",
        "https://ambridge.io/faq"
      ]
    },
    {
      "id": "signing-004",
      "question": "How can developers integrate document signing?",
      "answer": "Signing is available through the Signatures API with typed SDKs, idempotent endpoints and signed webhooks for status changes. A sandbox mirrors production behaviour so flows can be built and tested before going live.",
      "category": "signing",
      "urls": [
        "https://ambridge.io/products/digital-signature",
        "https://ambridge.io/developers/api-documentation",
        "https://ambridge.io/faq"
      ]
    },
    {
      "id": "signing-005",
      "question": "How is a signed document verified later?",
      "answer": "Each signed document is sealed so that any later change is detectable, and it is accompanied by the Signing Log. A recipient, auditor or counterparty can check the document's integrity and review the recorded evidence about the signers and the session.",
      "category": "signing",
      "urls": [
        "https://ambridge.io/products/digital-signature",
        "https://ambridge.io/faq"
      ]
    },
    {
      "id": "attest-001",
      "question": "What is document attestation?",
      "answer": "Attestation is an institution formally standing behind a document it issues — a degree certificate, a transcript, a licence, an employment or financial statement — so that anyone receiving that document can confirm it is genuine and unaltered.",
      "category": "attestation",
      "urls": [
        "https://ambridge.io/products/document-attestation",
        "https://ambridge.io/faq"
      ]
    },
    {
      "id": "attest-002",
      "question": "How does Ambridge Attest work?",
      "answer": "An issuing institution submits a document through the Attestations API. Ambridge gives it a unique verification identity, seals it against tampering and generates a verifiable reference such as a QR code or document ID. Anyone holding the document can then resolve that reference and see the issuer's record.",
      "category": "attestation",
      "urls": [
        "https://ambridge.io/products/document-attestation",
        "https://ambridge.io/faq"
      ]
    },
    {
      "id": "attest-003",
      "question": "What is the difference between signing and attestation?",
      "answer": "Signing records that a party agreed to a document — the evidence is about intent. Attestation records that an institution issued a document and vouches for its contents — the evidence is about provenance. A contract is signed; a degree certificate is attested.",
      "category": "attestation",
      "urls": [
        "https://ambridge.io/products/document-attestation",
        "https://ambridge.io/products/digital-signature",
        "https://ambridge.io/faq"
      ]
    },
    {
      "id": "attest-004",
      "question": "Who typically uses document attestation?",
      "answer": "Universities and examination bodies issuing degrees and transcripts, professional bodies issuing licences and memberships, employers issuing letters, and any institution whose documents are routinely checked by third parties such as employers, regulators or immigration authorities.",
      "category": "attestation",
      "urls": [
        "https://ambridge.io/products/document-attestation",
        "https://ambridge.io/faq"
      ]
    },
    {
      "id": "verify-001",
      "question": "What is document verification?",
      "answer": "Document verification is the act of confirming that a document presented to you is intact and genuinely came from the issuer or signer it claims. It answers two questions: has this document been altered, and did the stated issuer really produce it?",
      "category": "verification",
      "urls": [
        "https://ambridge.io/products/document-attestation",
        "https://ambridge.io/faq"
      ]
    },
    {
      "id": "verify-002",
      "question": "How does digital document verification work with Ambridge?",
      "answer": "A verifier resolves the document's reference — a document ID, PIN or QR code — through the Verification API or the public verification page. Ambridge checks the document against the issuer's record and reports the issuer, the document's integrity and its current validity.",
      "category": "verification",
      "urls": [
        "https://ambridge.io/products/document-attestation",
        "https://ambridge.io/developers/api-documentation",
        "https://ambridge.io/faq"
      ]
    },
    {
      "id": "verify-003",
      "question": "Does the person verifying a document need an Ambridge account?",
      "answer": "Verification is designed for third parties who have no prior relationship with the issuer, so a document can be checked from the reference it carries without the verifier having to integrate anything.",
      "category": "verification",
      "urls": [
        "https://ambridge.io/products/document-attestation",
        "https://ambridge.io/faq"
      ]
    },
    {
      "id": "identity-001",
      "question": "What is digital identity verification?",
      "answer": "Digital identity verification establishes that a person is who they claim to be, remotely — typically by checking an identity document, matching it to the person's face, confirming the person is physically present through a liveness check, and recording the evidence.",
      "category": "identity",
      "urls": [
        "https://ambridge.io/products/identity-verification",
        "https://ambridge.io/faq"
      ]
    },
    {
      "id": "identity-002",
      "question": "What does Ambridge Identity provide?",
      "answer": "Identity provides KYC and Video KYC infrastructure: identity document checks, face match, liveness detection and assisted video sessions, each producing an audit trail that can be attached to the workflow that required the check.",
      "category": "identity",
      "urls": [
        "https://ambridge.io/products/identity-verification",
        "https://ambridge.io/faq"
      ]
    },
    {
      "id": "identity-003",
      "question": "What is Video KYC?",
      "answer": "Video KYC is a live, recorded video session in which an agent verifies a customer's identity documents and presence in real time. It is used where regulation or risk requires a human in the loop rather than an automated check alone.",
      "category": "identity",
      "urls": [
        "https://ambridge.io/products/identity-verification",
        "https://ambridge.io/faq"
      ]
    },
    {
      "id": "identity-004",
      "question": "How does identity verification relate to document signing?",
      "answer": "An identity check can be required before a signer is allowed to sign. The resulting signature carries the identity evidence in the same Signing Log, so the document shows not just that someone signed but that their identity was verified at the time.",
      "category": "identity",
      "urls": [
        "https://ambridge.io/products/identity-verification",
        "https://ambridge.io/products/digital-signature",
        "https://ambridge.io/faq"
      ]
    },
    {
      "id": "trust-001",
      "question": "What is digital trust infrastructure?",
      "answer": "Digital trust infrastructure is the shared machinery that lets organisations rely on people and documents they cannot inspect in person: identity checks, signatures, attestation, verification and the evidence that ties them together. It is consumed as an API rather than rebuilt inside every application.",
      "category": "trust",
      "urls": [
        "https://ambridge.io/trust-center",
        "https://ambridge.io/faq",
        "https://ambridge.io/"
      ]
    },
    {
      "id": "trust-002",
      "question": "What does trust infrastructure as a service mean?",
      "answer": "It means the identity, signing, attestation and verification layers are operated for you and integrated through APIs, in the same way communications platforms provide messaging and telephony. Your product keeps its own workflow and interface; Ambridge supplies the trust primitives and the evidence trail underneath.",
      "category": "trust",
      "urls": [
        "https://ambridge.io/trust-center",
        "https://ambridge.io/faq",
        "https://ambridge.io/"
      ]
    },
    {
      "id": "trust-003",
      "question": "What evidence does Ambridge produce?",
      "answer": "Signed and attested documents are tamper-evident and accompanied by an audit record covering the parties, the events and the checks that were performed. The evidence is designed to be handed to an auditor, a regulator or a counterparty rather than only read inside the product.",
      "category": "trust",
      "urls": [
        "https://ambridge.io/trust-center",
        "https://ambridge.io/faq"
      ]
    },
    {
      "id": "dev-001",
      "question": "Does Ambridge provide APIs?",
      "answer": "Yes. Ambridge exposes a Signatures API, an Attestations API, a Verification API and an Identity API across one authenticated surface, with typed SDKs, idempotent endpoints and signed webhooks.",
      "category": "developers",
      "urls": [
        "https://ambridge.io/developers/api-documentation",
        "https://ambridge.io/faq"
      ]
    },
    {
      "id": "dev-002",
      "question": "How does integration work?",
      "answer": "You authenticate with a scoped API key, call the service you need, and receive webhooks as the state changes. A sandbox behaves like production, so signing, attestation and identity flows can be built end to end before any live traffic.",
      "category": "developers",
      "urls": [
        "https://ambridge.io/developers/api-documentation",
        "https://ambridge.io/faq"
      ]
    },
    {
      "id": "dev-003",
      "question": "What kinds of applications can use Ambridge?",
      "answer": "Anything that needs a document signed, issued or checked, or a person verified: lending and onboarding flows, HR and education systems, government services, healthcare consent, and SaaS platforms embedding trust features for their own customers.",
      "category": "developers",
      "urls": [
        "https://ambridge.io/developers/api-documentation",
        "https://ambridge.io/faq"
      ]
    },
    {
      "id": "security-001",
      "question": "How does Ambridge approach security?",
      "answer": "Security is built around tamper evidence by default, encryption in transit and at rest, least-privilege access with scoped API keys and role-based access control, full administrative audit logging, and regular security testing.",
      "category": "security",
      "urls": [
        "https://ambridge.io/security",
        "https://ambridge.io/trust-center",
        "https://ambridge.io/faq"
      ]
    },
    {
      "id": "security-002",
      "question": "Is Ambridge SOC 2 compliant?",
      "answer": "Ambridge follows the SOC 2 trust service principles — security, availability, processing integrity, confidentiality and privacy — with controls monitored year-round and examined annually. SOC 2 reports are made available to customers and prospects under NDA.",
      "category": "security",
      "urls": [
        "https://ambridge.io/security/soc-2",
        "https://ambridge.io/security",
        "https://ambridge.io/faq"
      ]
    },
    {
      "id": "security-003",
      "question": "Is Ambridge ISO 27001 certified?",
      "answer": "Ambridge operates an information security management system aligned to ISO/IEC 27001, covering risk assessment, documented controls, internal audit and management review across the services that handle customer documents and identity data.",
      "category": "security",
      "urls": [
        "https://ambridge.io/security/iso-27001",
        "https://ambridge.io/security",
        "https://ambridge.io/faq"
      ]
    },
    {
      "id": "security-004",
      "question": "How does Ambridge protect documents and identity data?",
      "answer": "Documents and identity evidence are encrypted in transit and at rest, access is restricted by role and scoped credentials, key management is separated from application access, and every administrative action is logged.",
      "category": "security",
      "urls": [
        "https://ambridge.io/security",
        "https://ambridge.io/products/identity-verification",
        "https://ambridge.io/faq"
      ]
    },
    {
      "id": "security-005",
      "question": "Where is data processed and can I choose the region?",
      "answer": "Ambridge offers regional processing so regulated customers can keep data in a chosen jurisdiction, with documented sub-processors. The data centre compliance matrix lists locations and the standards each one is covered by.",
      "category": "security",
      "urls": [
        "https://ambridge.io/security/data-centers",
        "https://ambridge.io/security",
        "https://ambridge.io/faq"
      ]
    },
    {
      "id": "security-006",
      "question": "How does Ambridge handle GDPR?",
      "answer": "Ambridge supports GDPR obligations through data processing terms, data residency options within the EU, defined retention, documented sub-processors and mechanisms for handling data subject requests.",
      "category": "security",
      "urls": [
        "https://ambridge.io/security/gdpr",
        "https://ambridge.io/faq"
      ]
    },
    {
      "id": "pricing-001",
      "question": "How is Ambridge priced?",
      "answer": "Pricing is per service and usage-based: Sign and Attest have published tiers based on volume, and Identity is quoted individually because KYC and Video KYC costs depend on jurisdiction, check types and session volumes.",
      "category": "pricing",
      "urls": [
        "https://ambridge.io/pricing",
        "https://ambridge.io/faq"
      ]
    },
    {
      "id": "pricing-002",
      "question": "Can I try Ambridge before committing?",
      "answer": "A sandbox that mirrors production is available so teams can build and evaluate signing, attestation and identity flows before moving to a paid plan.",
      "category": "pricing",
      "urls": [
        "https://ambridge.io/pricing",
        "https://ambridge.io/developers/api-documentation",
        "https://ambridge.io/faq"
      ]
    }
  ]
}