canonical: https://jentic.com/apis/swaggerhub.susannah/anomaly-federal-api # Susannah Anomaly Federal API 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. ## For AI agents Programmatically create a new alert subscription, retrieve a specific alert subscription. Covers 8 operations with bearer authentication. ## Scope Does not handle payments, communications, or crm - use for developer tools only. ## Capabilities - Create a new alert subscription - Retrieve a specific alert subscription - Update an alert subscription - Estimate reach for a network activation - Activate the Enigma Mobile Alert Network ## Use cases ### 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. Example prompt: 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. Example prompt: 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. Example prompt: Search Jentic for 'create a new alert subscription', load the operation schema, and execute with Jentic-managed credentials ## Key endpoints | Method | Path | Description | | --- | --- | --- | | POST | `/alert-subscriptions` | Create a new alert subscription | | GET | `/alert-subscriptions/{name}` | Retrieve a specific alert subscription | | PATCH | `/alert-subscriptions/{name}` | Update an alert subscription | | GET | `/alerts` | Retrieve triggered alerts | | POST | `/enigma-network-activation/estimate` | Estimate reach for a network activation | | POST | `/enigma-network-activation` | Activate the Enigma Mobile Alert Network | | GET | `/enigma-network-activation/{name}` | Retrieve activation details and reach | | POST | `/sightings/query` | Query sightings data | ## Key resources - **Anomaly Alert Subscriptions** — Manage subscriptions for real-time alerts based on validated UAP sightings. - **Create** a new subsc - **Anomaly Alerts** — Retrieve real-time alerts generated from configured subscriptions. - **Enigma Network Activation** — On-demand activation of the Enigma Mobile Alert Network. - **Sightings** — Query UAP sighting data. ## Why Jentic - **Setup:** Wiring the Anomaly Federal API by hand means handling its bearer auth, targeting the anomalyfederal.io host, and managing alert subscription and activation calls and retries yourself. Through Jentic you install once, import the Anomaly Federal API from the API Directory, store the token once, and your agent calls it. - **Permission scoping:** This API puts the subscription name in the URL path (`/alert-subscriptions/{name}`), so a rule can pin your agent to one alert subscription: it can read and patch that subscription and read alerts and nothing else. You choose the operations it may call, so writes like network activation or sightings queries are not included unless you add them. - **Credential handling:** 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. - **Discovery method:** 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. ## Related APIs - **Github** — Alternative developer tools API - **Gitlab** — Alternative developer tools API ## FAQ ### 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.