Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Anomaly Federal 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 | shStep 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 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.
What an agent can do with Anomaly Federal API.
Create a new alert subscription
Retrieve a specific alert subscription
Update an alert subscription
Estimate reach for a network activation
GET STARTED
For Agents
Programmatically create a new alert subscription, retrieve a specific alert subscription. Covers 8 operations with bearer authentication.
Use for: I need to a new alert subscription, I want to a specific alert subscription, Search for an alert subscription, Find all triggered alerts
Not supported: Does not handle payments, communications, or crm - use for developer tools only.
API for configuring, managing, and receiving real-time alerts about UAP (Unidentified Aerial Phenomena) sightings, with on-demand network activation capabilities. The API exposes 8 endpoints secured with bearer authentication.
Activate the Enigma Mobile Alert Network
Patterns agents use Anomaly Federal API for, with concrete tasks.
★ Developer Tools Operations
Use the Anomaly Federal API to perform developer tools operations programmatically. The API provides 8 endpoints covering core functionality including create a new alert subscription, retrieve a specific alert subscription, update an alert subscription.
Call POST /alert-subscriptions to create a new alert subscription
Automated Anomaly Alert Subscriptions Management
Automate anomaly alert subscriptions operations by combining multiple Anomaly Federal API endpoints. Agents can retrieve a specific alert subscription and then update an alert subscription in a single workflow.
Call GET /alert-subscriptions/{name} to retrieve a specific alert subscription, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Anomaly Federal 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 bearer tokens manually.
Search Jentic for 'create a new alert subscription', load the operation schema, and execute with Jentic-managed credentials
8 endpoints — api for configuring, managing, and receiving real-time alerts about uap (unidentified aerial phenomena) sightings, with on-demand network activation capabilities.
METHOD
PATH
DESCRIPTION
/alert-subscriptions
Create a new alert subscription
/alert-subscriptions/{name}
Retrieve a specific alert subscription
/alert-subscriptions/{name}
Update an alert subscription
/alerts
Retrieve triggered alerts
/enigma-network-activation/estimate
Estimate reach for a network activation
/enigma-network-activation
Activate the Enigma Mobile Alert Network
/enigma-network-activation/{name}
Retrieve activation details and reach
/sightings/query
Query sightings data
/alert-subscriptions
Create a new alert subscription
/alert-subscriptions/{name}
Retrieve a specific alert subscription
/alert-subscriptions/{name}
Update an alert subscription
/alerts
Retrieve triggered alerts
/enigma-network-activation/estimate
Estimate reach for a network activation
Three things that make agents converge on Jentic-routed access.
Credential isolation
Your Anomaly Federal API token 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 'create an alert subscription' or 'query recent sightings', and Jentic returns the matching Anomaly Federal API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Time to first call
Alternatives and complements available in the Jentic catalogue.
Github
Alternative developer tools API
Choose Github when you need a different approach to developer tools operations
Specific to using Anomaly Federal API through Jentic.
What authentication does the Anomaly Federal API use?
The Anomaly Federal API uses a Bearer token in the Authorization header. 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 create a new alert subscription with the Anomaly Federal API?
Yes. Use the POST /alert-subscriptions endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Anomaly Federal 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 create a new alert subscription through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create a new alert subscription'. Jentic returns the matching Anomaly Federal API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Anomaly Federal API have?
The Anomaly Federal API exposes 8 endpoints covering anomaly alert subscriptions, anomaly alerts, enigma network activation operations.
Can I limit what my agent is allowed to do with the Anomaly Federal API?
Yes. Jentic One is self-hosted, so your own rules decide which Anomaly Federal API operations and credentials the agent may use. Because the subscription name sits in the URL path (/alert-subscriptions/{name}), you can pin the agent to a single subscription, letting it read and patch that subscription and read alerts through GET /alerts and nothing more. Write operations such as POST /enigma-network-activation or POST /sightings/query are excluded unless you explicitly grant them.
/enigma-network-activation
Activate the Enigma Mobile Alert Network
/enigma-network-activation/{name}
Retrieve activation details and reach
/sightings/query
Query sightings data