Cyfe Push API
68
AI ReadinessAI-Aware (B+)68/100
Official vendor OpenAPI document · agent-readyAnalyticsBusiness Intelligencenone1 EndpointsREST
For Agents
Push custom metric data points into a Cyfe dashboard widget so an agent's own measurements show up in a shared business dashboard.
Use for: I need to push a daily revenue total into a Cyfe widget, Send weekly active user counts to a Cyfe dashboard, Update a Cyfe custom widget with the latest agent task completion rate, Backfill the last 30 days of conversion data into Cyfe
Not supported: Does not handle dashboard creation, widget configuration, or read-back of stored data - use for pushing custom metric values into existing Cyfe widgets only.
Cyfe is a business dashboard platform that aggregates KPIs from marketing, sales, finance, and product systems into a single view. The Push API exposes one POST endpoint for streaming custom metrics into a Cyfe widget, identified by a per-widget URL token. It is the integration surface used when an internal system, script, or AI agent needs to render its own data in a Cyfe dashboard alongside the platform's prebuilt connectors.
Install Jentic One Beta
Connect the Cyfe Push API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Cyfe Push 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.
1
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%2Fcyfe.com%2Fcyfe" | sh2
Step 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%2Fcyfe.com%2Fcyfe" | 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.
Capabilities
What an agent can do with Cyfe Push API.
Push a single time-series data point into a Cyfe custom widget by widget ID
Stream batch metric updates as JSON payloads to keep a dashboard widget current
Backfill historical data into a Cyfe widget by including explicit date fields in the payload
Pipe agent-generated KPIs into an existing Cyfe dashboard without writing a Cyfe connector
Treat the per-widget URL token as a scoped credential to avoid sharing account-level secrets
Use Cases
Patterns agents use Cyfe Push API for, with concrete tasks.
★ Custom KPI Dashboard Feed
A team running a Cyfe dashboard for executives wants to add a metric that is not covered by Cyfe's prebuilt connectors, such as agent-completed support tickets or model-cost-per-task. They configure a custom widget, take its push URL, and have a scheduled agent POST the latest value once an hour. The widget renders alongside the platform's native integrations without any custom dashboard code.
POST {"data":[{"Date":"2026-06-10","Tickets":42}]} to /api/push/{widget_id} once per hour.
Historical Backfill Into a New Widget
When a team adds a new Cyfe widget mid-quarter, they need the chart to start with historical context rather than a single fresh data point. The Push API accepts an array of dated entries, so an agent can iterate through the past 30 or 90 days of stored values and POST them in one or two requests, populating the widget's history.
Build a JSON array of 30 daily values from the data warehouse and POST it to /api/push/{widget_id} as a single request.
Agent-Driven Operational Metrics
An AI agent supervising a fleet of automation jobs publishes its own observability metrics to a Cyfe widget so non-technical stakeholders can see throughput and success rate without opening logs. The agent reads its own state, computes the metric, and pushes the value, turning agent activity into a first-class dashboard tile.
Read the agent's task log for the last hour, compute success rate, and POST {"data":[{"Date":"NOW","SuccessRate":97.2}]} to /api/push/{widget_id}.
Key Endpoints
1 endpoints — cyfe is a business dashboard platform that aggregates kpis from marketing, sales, finance, and product systems into a single view.
METHOD
PATH
DESCRIPTION
POST
/api/push/{widget_id}
Push data to a Cyfe custom dashboard widget
POST
/api/push/{widget_id}
Push data to a Cyfe custom dashboard widget
Jentic AI Readiness Score
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.
C
Cyfe Push API
- AI-Aware (B+)68/100
84
Foundational Compliance63
Developer Experience & Jentic Compatibility44
AI-Readiness & Agent Experience94
Agent Usability100
Security100
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
84
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: ASignals: 4
99%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
100%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
35%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
63
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: B-Signals: 4
0%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
50%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
44
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: DSignals: 4
25%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
100%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
50%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
100
Security
Trust, risk posture, and security compliance.
Grade: A+Signals: 1
100%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
100
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: A+Signals: 1
100%
Descriptive Richness
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>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Cyfe Push API by hand means keeping each widget's push URL secret, formatting the metric payload, and posting it to the right widget yourself. Through Jentic you install once, import the Cyfe Push API from the API Directory, store the widget push URL once, and your agent calls it.
Permission scoping
Cyfe puts the widget id in the URL path (/api/push/{widget_id}), so a rule can pin your agent to pushing values into one widget and nothing else. Pushing metrics is the only operation this API exposes, so the agent cannot read back or reconfigure the dashboard.
Credential isolation
Your Cyfe widget push URL is treated as a secret, stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'push a metric value to a Cyfe dashboard', and Jentic returns the Cyfe Push operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Cyfe Push API through Jentic.
What authentication does the Cyfe Push API use?
Cyfe's Push API uses a per-widget URL token rather than a global API key. Each custom widget has its own widget_id which is treated as a shared secret in the URL path. Through Jentic the widget URL is stored in the encrypted vault and surfaced to the agent as a scoped runtime credential, so the raw URL never lands in chat history.
Can I push multiple data points in one Cyfe API call?
Yes. The /api/push/{widget_id} endpoint accepts an array under the data key, so you can send a batch of dated entries in a single POST. This is how historical backfill works when you add a new widget mid-quarter.
What are the rate limits for the Cyfe Push API?
Cyfe does not document explicit rate limits for the Push API in the spec. The platform's published guidance is to push no more frequently than once per minute per widget; for higher-frequency telemetry, batch values into a single payload rather than firing many small requests.
How do I publish an agent's KPI to Cyfe through Jentic?
Install pip install jentic and run an agent with the search query 'push data to a Cyfe dashboard widget'. Jentic returns the POST /api/push/{widget_id} operation with its input schema; the agent constructs the JSON payload (Date, plus one or more numeric fields) and calls execute.
Can I read data back from a Cyfe widget through this API?
No. The Push API is write-only. There is no endpoint for retrieving widget contents, dashboards, or account metadata; the only operation exposed is POST /api/push/{widget_id}.
Is the Cyfe Push API free?
Push API access is included with all paid Cyfe plans, including the entry-level Starter tier. Cyfe has historically offered a free tier with a small number of widgets which also includes Push API support, so single-widget integrations can run at no cost.
Can I limit what my agent is allowed to do with the Cyfe Push API?
Yes. Because your Jentic One instance is self-hosted, your own rules decide which operations and credentials the agent may use. Cyfe puts the widget id in the URL path (POST /api/push/{widget_id}), so you can pin the agent to pushing values into one specific widget and nothing else. Pushing metrics is the only operation this API exposes, so the agent cannot read back stored data or reconfigure the dashboard.
GET STARTED