Install Jentic One Beta

Connect the Dregs API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Dregs 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%2Fdregs.com%2Fdregs" | sh

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%2Fdregs.com%2Fdregs" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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 Dregs API.

Send tracking events that score the identities and devices behind them

Read fraud scores, score history, and analysis for an identity

Group identities and manage their device links by fingerprint

Define, preview, and manage escalation rules that flag risky identities

Review and update escalations and read an escalation summary

GET STARTED

Start building with Dregs API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Dregs API for, with concrete tasks.

★ Agent-driven fraud triage

An AI agent connected through Jentic pulls the identities that need attention, reads each one's fraud score and analysis, and reviews the open escalations so an analyst starts the day with the riskiest cases summarized rather than scrolling a dashboard. The agent reads the scoring and escalation data on demand and highlights what changed.

List the identities flagged as needing attention, read each one's latest score, and summarize the open escalations

Event ingestion and scoring

Applications send user and device events to Dregs so each identity is scored for fraud risk as activity happens. The event-ingest endpoint accepts either the secret key or a browser-safe public key, and the resulting score and analysis are then readable per identity and device.

Send a tracking event for an identity, then read the identity's updated score and its device links

Escalation rule management

Risk teams define escalation rules that flag identities crossing a threshold, preview a rule before enabling it, and route matches to notification channels. Dregs exposes list, create, preview, and update operations for rules plus the escalations they produce.

Preview an escalation rule that flags identities above a risk threshold, then create it if the preview looks right

Risk dashboards and summaries

Teams read Dregs dashboard endpoints to track score distribution, rule activity, and recently active identities over time. These summaries give an agent the aggregate picture it needs to report on fraud trends without re-deriving them from raw events.

Read the score-distribution and rule-activity summaries and report how risk has shifted

Key Endpoints

58 endpoints — the dregs api ingests tracking events and returns fraud scores and risk analysis for the identities and devices behind them.

METHOD

PATH

DESCRIPTION

POST

/api/events

Receive a tracking event

GET

/api/identities/{id}/scores

Get scores for an identity

POST

/api/identities/{id}/actions/analyze

Analyze an identity

GET

/api/devices/{fingerprint}

Get a device by fingerprint

GET

/api/escalations

List escalations

POST

/api/escalation-rules

Create an escalation rule

GET

/api/dashboard/stats

Read dashboard stats

POST

/api/events

Receive a tracking event

GET

/api/identities/{id}/scores

Get scores for an identity

POST

/api/identities/{id}/actions/analyze

Analyze an identity

GET

/api/devices/{fingerprint}

Get a device by fingerprint

GET

/api/escalations

List escalations

POST

/api/escalation-rules

Create an escalation rule

GET

/api/dashboard/stats

Read dashboard stats

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring Dregs by hand means handling its Bearer auth, keeping the admin secret key off the browser while allowing the public key on the event and device endpoints, and managing escalation rules and channels yourself. Through Jentic you install once, import Dregs from the API Directory, store the key once, and your agent calls it.

Permission scoping

Dregs carries identity, device, and escalation ids in the URL path, so a rule can pin your agent to the operations you pick, such as ingesting events and reading scores. You choose the operations it may call, so destructive ones like deleting an escalation rule or a channel are not included unless you add them.

Credential isolation

Your Dregs secret key is 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 'read fraud scores for an identity' or 'send a tracking event', and Jentic returns the matching Dregs operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Dregs API through Jentic.

What authentication does the Dregs API use?

The Dregs API authenticates with a secret key sent as a Bearer token in the Authorization header per its OpenAPI spec. A browser-safe public key, also sent as a Bearer token, is additionally accepted on the event-ingest and device-read endpoints. Through Jentic the keys are stored once and injected at call time so they never enter the agent's prompt.

Can I read fraud scores for an identity with the Dregs API?

Yes. Each identity exposes its current scores, score history, reviews, links, and analysis, and you can request a fresh analysis or review through dedicated action endpoints. Devices are read by fingerprint and carry their own risk signals.

What are the rate limits for the Dregs API?

The OpenAPI spec does not publish fixed rate limits. Check the Dregs dashboard and documentation for the limits that apply to your team's credentials before sending high volumes of events.

Is there a Dregs API MCP server?

You don't need an MCP server to give your agent the Dregs API. Jentic connects it directly from the API Directory: import it, store your key once, and your agent sends events and reads scores on demand without loading another server's tool definitions into its context.

Can I limit what my agent is allowed to do with the Dregs API?

Yes. Write a rule that allows only the event-ingest and score-read operations, so the agent can submit events and read fraud scores but cannot change escalation rules or delete channels, and every call it makes is logged for review.

How do I triage fraud risk with the Dregs API through Jentic?

Search Jentic for 'read fraud scores for an identity', add the Dregs API from the directory, and store your secret key once; your agent can then pull flagged identities and read their scores on demand. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Dregs API

AI ReadinessAI-Aware (B)64/100

See full scorecard

Official vendor OpenAPI document · agent-readySecurityThreat Detectionbearer58 EndpointsREST

For Agents

Send tracking events to score identities and devices for fraud risk, read their scores and analysis, and manage escalation rules that flag risky activity.

Use for: Send a tracking event for an identity and read its fraud score, Get the score history for a specific identity, Check which identities need attention right now, Analyze an identity and request a review

Not supported: Does not process payments, verify identity documents, or chargeback-dispute transactions. Use for fraud scoring, risk analysis, and escalation only.

The Dregs API ingests tracking events and returns fraud scores and risk analysis for the identities and devices behind them. It records identities, groups them, links their devices by fingerprint, and keeps a score history and analysis for each, while escalation rules and notification channels flag the identities that cross a threshold. Datasets and mappings feed the scoring, and a set of dashboard endpoints summarize score distribution, rule activity, and which identities need attention.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: ASignals: 4

96%

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).

50%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B-Signals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

46%

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.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: DSignals: 4

26%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

59%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

93%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: B-Signals: 1

60%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A-Signals: 1

71%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Dregs API to your agent

Capabilities

Start building with Dregs API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Dregs API

Jentic AI Readiness Score

Dregs API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness