Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Alpha Tracker API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fmanager.alphatracker.co.uk%2Falphatracker" | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fmanager.alphatracker.co.uk%2Falphatracker" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
What an agent can do with Alpha Tracker API.
Create and search survey projects by criteria
Register sites and the buildings that belong to them
Record samples and survey items against a project
Schedule, update, and cancel project appointments
Run saved reports by category and download project files
GET STARTED
Retrieve quotations and repair instructions
Send re-inspection data to a surveyor's handset
Patterns agents use Alpha Tracker API for, with concrete tasks.
★ Agent-managed survey intake
An AI agent handling inbound survey requests creates a project, registers the site and its buildings, and schedules the first appointment, all against the Alpha Tracker API. Because the API exposes project, site, building, and appointment operations, the agent can take a job from enquiry to a booked survey. Through Jentic the agent discovers each operation by intent and the two required headers are supplied at call time.
Create a project, register its site and building, and schedule the first appointment for the survey
Sample and survey-item capture
Surveyors on site record the samples they collect and the items they inspect. The Alpha Tracker API accepts samples and survey items against a specific project number and returns the list back, so a mobile workflow can push field data into the central system and read it back for reporting without manual re-entry.
Record the samples collected on a project and then list the project's survey items to confirm they were saved
Report generation and file retrieval
Once fieldwork is done, a team needs the certificates and reports for a project. The Alpha Tracker API lists reports by category, runs a named report, and downloads project files including the bulk certificate, so an agent can assemble a client's deliverables from the stored project data.
List the reports in a category, run the required report for a project, and download the resulting certificate file
35 endpoints — the alpha tracker api drives the alpha tracker asbestos management software, letting an application create and search survey projects, sites, and buildings and track their work through to completion.
METHOD
PATH
DESCRIPTION
/projects
Create a project
/projects/search
Search projects by criteria
/sites
Create a site
/samples/{projectNumber}
Record samples for a project
/appointments/{projectNumber}
Create an appointment for a project
/reports/{category}/{reportName}
Run a saved report
/projects
Create a project
/projects/search
Search projects by criteria
/sites
Create a site
/samples/{projectNumber}
Record samples for a project
/appointments/{projectNumber}
Create an appointment for a project
/reports/{category}/{reportName}
Run a saved report
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Alpha Tracker API by hand means sending the right two headers on every call, learning the project-number and site-id path structure, and parsing report and file downloads yourself. Through Jentic you install once, import it from the API Directory, store the api key and client id once, and your agent calls it.
Permission scoping
Alpha Tracker puts the project number and site id in the URL path, so a rule can pin your agent to specific projects and the operations you pick. You choose the operation set, so the delete operations on projects and sites are not included unless you add them.
Credential isolation
Your Alpha Tracker api key and client id are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'create a survey project' or 'run a report', and Jentic returns the matching Alpha Tracker operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Alternatives and complements available in the Jentic catalogue.
Specific to using Alpha Tracker API through Jentic.
What authentication does the Alpha Tracker API use?
The Alpha Tracker API expects two headers on each call, per its OpenAPI spec: an api key in the x-api-key header and a client identifier in the client-id header, both issued by Alpha Tracker support. Through Jentic both values are stored once and injected at call time, so they never enter the agent's prompt, logs, or context.
Can I run reports and download certificates with the Alpha Tracker API?
Yes. The API lists the saved reports in a category, runs a named report for a project, and downloads project files including the bulk certificate. An agent can list the reports available, run the one it needs, and fetch the resulting file for a client's project.
What are the rate limits for the Alpha Tracker API?
The OpenAPI spec does not define numeric rate limits. Have your agent back off when it receives an HTTP 429 response, and contact Alpha Tracker support for the current limits that apply to your client id.
Is there an Alpha Tracker MCP server?
You don't need an MCP server to give your agent the Alpha Tracker API. Jentic connects it directly from the API Directory: import it, store your api key and client id once, and your agent calls it. Operations are discovered on demand, so no extra tool definitions sit in the agent's context.
Can I limit what my agent is allowed to do with the Alpha Tracker API?
Yes. Alpha Tracker puts the project number and site id in the URL path, such as the project and site operations, so a rule can pin your agent to the projects and the operations you pick, letting it create samples and run reports without the delete operations unless you add them. Every call it makes is logged.
How do I create a survey project through Jentic?
Search Jentic for an intent such as 'create a new survey project' and it returns the matching project operation with its input schema, so your agent posts the project details and reads back the project number. To run it on your own infrastructure, install Jentic One from its GitHub repo.
Know of an official OpenAPI document? Contribute it →
For Agents
Create and search asbestos survey projects, sites, and buildings, record samples and survey items, schedule appointments, run saved reports, and download project files. Built for the Alpha Tracker surveying workflow.
Use for: Create a new survey project, Search for projects matching a reference, Register a site and its buildings, Record samples collected on a project
Not supported: Does not handle accounting, payroll, or laboratory analysis. Use for managing asbestos survey projects, sites, samples, appointments, and reports only.
The Alpha Tracker API drives the Alpha Tracker asbestos management software, letting an application create and search survey projects, sites, and buildings and track their work through to completion. It records samples and survey items against a project, retrieves quotations and repair instructions, schedules and updates appointments, lists staff, and runs saved reports by category. It also downloads project files and sends re-inspection data to a surveyor's handset.
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
Base layer of spec validity and structural soundness.
Aggregated quality score from linter diagnostics, weighted by severity.
Percentage of `$ref` references that resolve successfully.
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
Structural correctness score based on schema issues using logarithmic dampening.
Clarity, completeness, and ingestion readiness for developers and tooling.
How richly the API is illustrated with examples.
Percentage of examples that conform to their schemas.
Percentage of operations with complete response definitions (success, client error, server error).
Health of API ingestion, bundling, and resolution within Jentic pipelines.
Semantic breadth, depth, and agent comprehension for AI systems.
Coverage of descriptions across API elements.
Coverage of RFC 9457 Problem Details for error responses.
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
Coverage of summaries across operations/tags/info.
Functional utility, complexity comfort, and AI orchestration readiness.
Agent comfort level based on API operational and structural complexity.
Trust, risk posture, and security compliance.
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
Findability, semantic richness, and reasoning readiness.
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>