Prophecy.io
Prophecy is an AI-native, low-code data engineering and analytics platform for building, running, and managing data pipelines across SQL and Apache Spark environments on Databricks, Snowflake, and BigQuery. Data teams compose pipelines visually with gems (or natural language via the AI Copilot), and Prophecy generates clean Spark/SQL code committed to Git. The platform exposes a REST API (the Prophecy Orchestration/Deployment API) for programmatically managing fabrics, connections, secrets, deploying projects, and triggering pipeline runs and data tests, authenticated with per-user Personal Access Tokens. A companion CLI, the Prophecy Build Tool (PBT), integrates Prophecy projects into external CI/CD such as GitHub Actions and Jenkins.
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 Prophecy.io the way a machine reads it — 9 machine-readable artifacts across 5 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 — Prophecy.io scores 51.3/100 (developing), with a separate agent-readiness read of 51/100 (agent ready). 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 Prophecy.io
Each block below is one kind of artifact we hold for Prophecy.io. 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 5
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.
Prophecy.io Connections API
The Connections API from Prophecy.io — 2 operation(s) for connections.
Prophecy.io Fabrics API
The Fabrics API from Prophecy.io — 2 operation(s) for fabrics.
Prophecy.io Pipeline Runs API
The Pipeline Runs API from Prophecy.io — 3 operation(s) for pipeline runs.
Prophecy.io Project Deployment API
The Project Deployment API from Prophecy.io — 1 operation(s) for project deployment.
Prophecy.io Secrets API
The Secrets API from Prophecy.io — 2 operation(s) for secrets.
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.
prophecyio-mcp.yml
MCP SERVERSecurity Posture 3
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.
Resources
Every other property we hold for Prophecy.io — 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 3
Portal, sign-up, and the first successful call
Documentation 3
Reference material describing how the API behaves
Agent Surfaces 3
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 5
Pagination, idempotency, versioning, errors, and events
Build 4
SDKs, sample code, and the tooling you integrate with
Access & Security 4
Authentication, authorization, and security posture
Operate 4
Status, limits, changes, and where to get help
Commercial 1
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/prophecyio · machine-readable index on apis.io