Beaconcure website screenshot

Beaconcure

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.

Beaconcure publishes 1 API on the APIs.io network. Tagged areas include Company, Clinical Trials, Clinical Data, Life Sciences, and Pharmaceuticals.

Beaconcure’s developer surface includes documentation, engineering blog, support, authentication, and 8 more developer resources.

18.0/100 emerging ▬ flat Agent 9/100 agent aware Full breakdown ↓
scored 2026-08-17 · rubric v0.11.0
1 APIs
CompanyClinical TrialsClinical DataLife SciencesPharmaceuticalsData ValidationQuality ControlArtificial IntelligenceBiometricsHealthcare

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-08-17 · rubric v0.11.0
Composite quality — 18.0/100 · emerging
Contract Quality 0.0 / 21
Developer Ergonomics 4.4 / 17
Commercial Clarity 3.6 / 17
Operational Transparency 0.6 / 11
Governance 0.0 / 10
Discoverability 5.7 / 9
Regulatory Posture 3.8 / 15
Agent readiness — 9/100 · agent aware
Machine-Readable Contract 0 / 18
Agentic Access Contract 0 / 10
MCP Server 0 / 12
Machine-Readable Auth 10 / 10
Idempotency 0 / 9
Stable Error Semantics 0 / 8
Request/Response Examples 0 / 7
Rate-Limit Signaling 0 / 7
Typed Event Surface 0 / 6
Agent Skills 0 / 5
Well-Known Catalog 0 / 4
Consent & Bot Identity 0 / 3
A2A Agent Card 0 / 8
Dry-Run / Simulate Mode 0 / 4
Regulatory Posture applies to this provider. Its tags matched the Health regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.
The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. This rating is computed from github.com/api-evangelist/beaconcure: open an issue to ask a question, or submit a pull request to add artifacts. Want it done for you? Prioritized profiling — $2,500 →

APIs 1

Individual APIs this provider publishes, each with its own machine-readable definition.

Beaconcure Verify API

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 r...

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Beaconcure Authentication

apiKey/ipAllowlist · 2 schemes

SECURITY

Beaconcure Domain Security

TLSv1.3 · DMARC

SECURITY

Resources

Documentation 1

Reference material describing how the API behaves

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 2

Pagination, idempotency, versioning, errors, and events

Build 1

SDKs, sample code, and the tooling you integrate with

Access & Security 2

Authentication, authorization, and security posture

Operate 1

Status, limits, changes, and where to get help

Commercial 2

Pricing, plans, and the legal terms of use

Company 2

The organization behind the API

Source (apis.yml)

apis.yml Raw ↑
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.20'
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'