aid: beaconcure name: Beaconcure description: 'Beaconcure is a clinical data technology company whose AI-enabled platform, Verify, automates the statistical analysis and reporting workflow for biometrics teams running clinical trials. Verify converts static Tables, Listings and Figures (TLFs) into machine-readable form and runs format, reference, within-table and cross-table validation checks, tracks quality-control progress in a shared review workspace, and captures every fix in an inspection-ready audit trail across its Essentials, Validate and Generate modules. Beaconcure also documents a customer-scoped Verify REST API that exposes near real-time QC data — deliverables, projects, protocols, users, files, suspected and verified outputs, and discrepancies — as JSON or CSV, though each customer receives a unique API version and endpoint behind an IP allowlist. Founded in Israel with US headquarters in Boston, the company works with top-10 pharmaceutical companies and contract research organizations.' image: https://beaconcure.com/wp-content/uploads/2025/06/Artboard-1-copy-e1749721689852.png url: https://raw.githubusercontent.com/api-evangelist/beaconcure/refs/heads/main/apis.yml x-type: company x-source: harvest:secondary-market specificationVersion: '0.23' created: '2026-08-06' modified: '2026-08-06' tags: - Company - Clinical Trials - Clinical Data - Life Sciences - Pharmaceuticals - Data Validation - Quality Control - Artificial Intelligence - Biometrics - Healthcare apis: - name: Beaconcure Verify API description: 'A REST API over Verify''s near real-time quality-control data. Beaconcure documents it as resource-oriented, accepting form-encoded request bodies and returning JSON (or CSV on request) with standard HTTP status codes and verbs. It exposes counts and detail for deliverables, projects, protocols, users and files, plus QC analysis results such as suspected and verified files, tables and figures and the discrepancies found. Each customer organization receives its own API version and endpoint URL, issued by Beaconcure''s customer success team and restricted to an IP allowlist supplied during onboarding; the API reads from a partial clone of the customer''s data rather than the live Verify application.' humanURL: https://beaconcure.com/api/ tags: - Clinical Data - Quality Control - Validation - Reporting properties: - type: Documentation url: https://beaconcure.com/api/ - type: Authentication url: authentication/beaconcure-authentication.yml - type: Conventions url: conventions/beaconcure-conventions.yml - type: Lifecycle url: lifecycle/beaconcure-lifecycle.yml maintainers: - FN: Kin Lane email: kin@apievangelist.com - FN: APIs.json email: info@apis.io common: - type: Website url: https://beaconcure.com/ - type: Documentation url: https://beaconcure.com/api/ - type: Blog url: https://beaconcure.com/resources/ - type: Support url: https://beaconcure.com/contact-us/ - type: GitHubOrganization url: https://github.com/Beaconcure-Inc - type: TermsOfService url: https://beaconcure.com/terms-of-use/ - type: PrivacyPolicy url: https://beaconcure.com/privacy-policy/ - type: Authentication url: authentication/beaconcure-authentication.yml - type: Conventions url: conventions/beaconcure-conventions.yml - type: Lifecycle url: lifecycle/beaconcure-lifecycle.yml - type: DomainSecurity url: security/beaconcure-domain-security.yml - type: LLMsTxt url: llms/beaconcure-llms.txt x-enrichment: date: '2026-08-06' status: minimal artifacts_added: 5 pass: local-v1 x-coverage: state: gated reason: customer-only-docs detail: The public Verify API page describes the REST surface in prose but issues no reference — each customer gets a unique API version and endpoint URL from Beaconcure's customer success team, reachable only from an IP allowlist supplied at onboarding. evidence: - url: https://beaconcure.com/api/ status: 200 - url: https://beaconcure.com/openapi.json status: 404 - url: https://beaconcure.com/docs status: 404 - url: https://beaconcure.com/llms.txt status: 404 - url: https://beaconcure.com/.well-known/agent-card.json status: 404 checked: '2026-08-06'