canonical: https://jentic.com/apis/swaggerhub.susannah/anomaly-federal-aerial-awareness-api

# Susannah Anomaly Federal Aerial Awareness API

Anomaly Federal's API for configuring, managing, and receiving real-time reports about anomalous aerial objects or activity, with on-demand mobile alert network activation. The API exposes 7 endpoints secured with bearer authentication.

## For AI agents

Programmatically create a new configuration to populate a feed of aerial activity reports, retrieve a specific configuration by unique name. Covers 7 operations with bearer authentication.

## Scope

Does not handle payments, communications, or crm - use for analytics only.

## Capabilities

- Create a new configuration to populate a feed of aerial activity reports
- Retrieve a specific configuration by unique name
- Update a configuration by unique name
- Estimate reach for a network activation
- Activate the Mobile Alert Network

## Use cases

### Analytics Operations

Use the Anomaly Federal Aerial Awareness API to perform analytics operations programmatically. The API provides 7 endpoints covering core functionality including create a new configuration to populate a feed of aerial activity reports, retrieve a specific configuration by unique name, update a configuration by unique name.

Example prompt: Call POST /activity-feed-configurations to create a new configuration to populate a feed of aerial activity reports

### Automated Aerial Activity Feed Management

Automate aerial activity feed operations by combining multiple Anomaly Federal Aerial Awareness API endpoints. Agents can retrieve a specific configuration by unique name and then update a configuration by unique name in a single workflow.

Example prompt: Call GET `/activity-feed-configurations/{name}` to retrieve a specific configuration by unique name, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Anomaly Federal Aerial Awareness 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 configuration to populate a feed of aerial activity reports', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/activity-feed-configurations` | Create a new configuration to populate a feed of aerial activity reports |
| GET | `/activity-feed-configurations/{name}` | Retrieve a specific configuration by unique name |
| PATCH | `/activity-feed-configurations/{name}` | Update a configuration by unique name |
| GET | `/activity-feeds` | Retrieve enriched aerial activity reports organized by type and name |
| POST | `/mobile-network-activation/estimate` | Estimate reach for a network activation |
| POST | `/mobile-network-activation` | Activate the Mobile Alert Network |
| GET | `/mobile-network-activation/{name}` | Retrieve activation details and reach |

## Key resources

- **Aerial Activity Feed** — Query, configure, and manage aerial activity feeds.
- **Mobile Alert Network Activation** — On-demand activation of the Mobile Alert Network.

## Why Jentic

- **Setup:** Wiring the Anomaly Federal Aerial Awareness API by hand means handling its JWT bearer auth, targeting the aerial-activity host, and managing feed configuration and activation calls and retries yourself. Through Jentic you install once, import the Anomaly Federal Aerial Awareness API from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** This API puts the configuration name in the URL path (`/activity-feed-configurations/{name}`), so a rule can pin your agent to one feed configuration: it can read and patch that configuration and read the feeds and nothing else. You choose the operations it may call, so writes like network activation are not included unless you add them.
- **Credential handling:** Your Anomaly Federal Aerial Awareness 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 aerial activity feed configuration' or 'estimate a mobile network activation', and Jentic returns the matching Anomaly Federal Aerial Awareness API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Mixpanel** — Alternative analytics API
- **Amplitude** — Alternative analytics API
- **Segment** — Complementary analytics API
- **Pendo** — Complementary analytics API

## FAQ

### What authentication does the Anomaly Federal Aerial Awareness API use?

The Anomaly Federal Aerial Awareness 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 configuration to populate a feed of aerial activity reports with the Anomaly Federal Aerial Awareness API?

Yes. Use the POST /activity-feed-configurations endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Anomaly Federal Aerial Awareness 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 configuration to populate a feed of aerial activity reports 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 configuration to populate a feed of aerial activity reports'. Jentic returns the matching Anomaly Federal Aerial Awareness API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Anomaly Federal Aerial Awareness API have?

The Anomaly Federal Aerial Awareness API exposes 7 endpoints covering aerial activity feed, mobile alert network activation operations.

### Can I limit what my agent is allowed to do with the Anomaly Federal Aerial Awareness API?

Yes. Because you run Jentic One yourself, your own rules decide which operations and credentials the agent may use. Since the configuration name sits in the URL path (`/activity-feed-configurations/{name}`), you can pin the agent to a single feed configuration so it only reads and patches that configuration and reads the activity feeds. Write operations like activating the Mobile Alert Network or estimating its reach stay out of scope unless you explicitly allow them.