Skip to content
GenomarkerDEVELOPERS
Request access
API referenceRequest access

Developers · Authentication

Authentication

Keys are workspace-scoped and actor-bound — a key is an identity, and every call it makes lands in actor provenance.

Authentication
$ export GENOMARKER_API_KEY=gm_key_…

curl https://api.genomarker.com/v1/whoami \
  -H "Authorization: Bearer $GENOMARKER_API_KEY"

{"workspace": "hjelm-lab", "actor_type": "human",
 "interface": "api", "scopes": ["runs:write"]}

MCP surface — assurance only

MCP tools
list_analysis_types
get_analysis_schema
list_assurance_profiles
validate_analysis_spec
submit_analysis · get_result
get_assurance_findings
get_evidence · verify_evidence
replay_evidence
get_sap · validate_against_sap

Deliberately narrow. Genomarker’s job is to assure computation — agents can gather scientific context elsewhere.

Actor provenance

Actor provenance JSON
{
  "actor_type": "agent",
  "interface": "mcp",
  "client": "helix-sci-agent",
  "model": "optional-identifier"
}