MINE
Mine (MineOS) is a data privacy, governance, and AI security posture management platform backed by Battery Ventures. Its MineOS product automates data mapping and inventory, data subject / privacy rights requests (DSR), consent management, vendor and third-party risk (TPRM) assessments, and AI governance (AISPM) for enterprises, while the MineApp helps individuals reclaim their personal data. The MineOS public API (OpenAPI 3.0.1, API-key Bearer auth, EU + US datacenter endpoints) exposes tickets / privacy requests, data-source systems, assessments and templates, employees and business units, AI agent and device discovery, and webhook subscriptions, plus a hosted remote MCP server for agent access.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles MINE the way a machine reads it — 26 machine-readable artifacts across 18 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — MINE scores 50.4/100 (developing), with a separate agent-readiness read of 82/100 (agent native). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile MINE
Each block below is one kind of artifact we hold for MINE. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 18
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
MINE Aispm API
The Aispm API from MINE — 1 operation(s) for aispm.
MINE AispmDeviceFlags API
The AispmDeviceFlags API from MINE — 1 operation(s) for aispmdeviceflags.
MINE AispmEnroll API
The AispmEnroll API from MINE — 2 operation(s) for aispmenroll.
MINE AispmEnrollmentTokens API
The AispmEnrollmentTokens API from MINE — 3 operation(s) for aispmenrollmenttokens.
MINE AispmIngest API
The AispmIngest API from MINE — 1 operation(s) for aispmingest.
MINE AispmInsights API
The AispmInsights API from MINE — 1 operation(s) for aispminsights.
MINE AispmPublicAgents API
The AispmPublicAgents API from MINE — 4 operation(s) for aispmpublicagents.
MINE AispmPublicDevices API
The AispmPublicDevices API from MINE — 2 operation(s) for aispmpublicdevices.
MINE Assessment API
The Assessment API from MINE — 8 operation(s) for assessment.
MINE AssessmentTemplate API
The AssessmentTemplate API from MINE — 1 operation(s) for assessmenttemplate.
MINE Employee API
The Employee API from MINE — 1 operation(s) for employee.
MINE EvidenceSearch API
The EvidenceSearch API from MINE — 1 operation(s) for evidencesearch.
MINE Partners API
The Partners API from MINE — 2 operation(s) for partners.
MINE PrivacyRightsPublic API
The PrivacyRightsPublic API from MINE — 1 operation(s) for privacyrightspublic.
MINE System API
The System API from MINE — 6 operation(s) for system.
MINE Test API
The Test API from MINE — 1 operation(s) for test.
MINE Tickets API
The Tickets API from MINE — 16 operation(s) for tickets.
MINE Webhooks API
The Webhooks API from MINE — 6 operation(s) for webhooks.
Scroll within the panel for all 18 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
mine-mcp.yml
MCP SERVERRate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Mine Rate Limits
RATE LIMITSEvent Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Mine Webhooks
ASYNCAPISecurity Posture 4
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for MINE — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 2
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 5
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 5
Pagination, idempotency, versioning, errors, and events
Build 2
SDKs, sample code, and the tooling you integrate with
Access & Security 6
Authentication, authorization, and security posture
Operate 3
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
← All providers · Data indexed from github.com/api-evangelist/mine · machine-readable index on apis.io