Sift API

Name: Sift API
Brand: Sift API
Availability: InStock

✓ Official Vendor SpecDeveloper ToolsSource Controlbasic14 EndpointsREST

For Agents

Programmatically send event, get user score. Covers 14 operations with basic authentication.

Install Jentic One Beta

Connect the Sift API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Sift 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | 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 Sift API.

Send Event

Get User Score

Rescore User

Apply Decision to User

GET STARTED

Start building with Sift API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Sift API for, with concrete tasks.

★ Developer Tools Operations

Use the Sift API to perform developer tools operations programmatically. The API provides 14 endpoints covering core functionality including send event, get user score, rescore user.

Call POST /v205/events to send event

Automated Events Management

Automate events operations by combining multiple Sift API endpoints. Agents can get user score and then rescore user in a single workflow.

Call GET /v205/users/{userId}/score to get user score, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Sift API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle basic tokens manually.

Search Jentic for 'send event', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

14 endpoints — sift's fraud detection and prevention api for sending events, retrieving scores, and managing decisions.

METHOD

PATH

DESCRIPTION

POST

/v205/events

Send Event

GET

/v205/users/{userId}/score

Get User Score

POST

/v205/users/{userId}/rescore

Rescore User

POST

/v3/accounts/{accountId}/users/{userId}/decisions

Apply Decision to User

GET

/v3/accounts/{accountId}/users/{userId}/decisions

Get User Decisions

POST

/v3/accounts/{accountId}/orders/{orderId}/decisions

Apply Decision to Order

GET

/v3/accounts/{accountId}/orders/{orderId}/decisions

Get Order Decisions

POST

/v3/accounts/{accountId}/sessions/{sessionId}/decisions

Apply Decision to Session

POST

/v205/events

Send Event

GET

/v205/users/{userId}/score

Get User Score

POST

/v205/users/{userId}/rescore

Rescore User

POST

/v3/accounts/{accountId}/users/{userId}/decisions

Apply Decision to User

GET

/v3/accounts/{accountId}/users/{userId}/decisions

Get User Decisions

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Your Sift credential 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 'send an event' or 'get a user risk score', and Jentic returns the matching Sift operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Time to first call

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Github

Alternative developer tools API

Choose Github when you need a different approach to developer tools operations

Alternative

Gitlab

Alternative developer tools API

Choose Gitlab when you need a different approach to developer tools operations

FAQs

Specific to using Sift API through Jentic.

What authentication does the Sift API use?

The Sift API uses HTTP Basic authentication with username and password. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

Can I send event with the Sift API?

Yes. Use the POST /v205/events endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the Sift API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

How do I send event through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'send event'. Jentic returns the matching Sift API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the Sift API have?

The Sift API exposes 14 endpoints covering events, scores, decisions operations.

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

Yes. Jentic One runs self-hosted, so your own rules decide which Sift operations and credentials the agent may use. Because Sift carries the user, order, and session ids in the URL path (for example /v3/accounts/{accountId}/users/{userId}/decisions), a rule can pin the agent to a single user or order so it only reads and posts decisions for that resource. You pick the exact operations it can call, such as sending an event or getting a user score, and anything you do not add stays unavailable to it.