canonical: https://jentic.com/apis/spyse.com/spyse

# Spyse API

Spyse is an internet assets search engine that provides comprehensive data on domains, IPs, SSL certificates, autonomous systems, CVEs, and emails. The API allows programmatic access to search, retrieve, and download internet asset data for security research and reconnaissance. The API exposes 41 endpoints secured with bearer authentication.

## For AI agents

Programmatically get account quota information, get domain details. Covers 41 operations with bearer authentication.

## Scope

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

## Capabilities

- Get account quota information
- Search domains
- Count domain search results
- Download domain search results
- Scroll search domains
- Trigger on-demand domain scan

## Use cases

### Security Operations

Use the Spyse API to perform security operations programmatically. The API provides 41 endpoints covering core functionality including get account quota information, get domain details, search domains.

Example prompt: Call GET /account to get account quota information

### Automated Account Management

Automate account operations by combining multiple Spyse API endpoints. Agents can get domain details and then search domains in a single workflow.

Example prompt: Call GET `/domain/{domain}` to get domain details, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Spyse 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 'get account quota information', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/account` | Get account quota information |
| GET | `/domain/{domain}` | Get domain details |
| POST | `/domain/search` | Search domains |
| POST | `/domain/search_count` | Count domain search results |
| POST | `/domain/search_download` | Download domain search results |
| POST | `/domain/scroll_search` | Scroll search domains |
| POST | `/domain/on_demand_scan` | Trigger on-demand domain scan |
| GET | `/ip/{ip}` | Get IP details |

## Key resources

- **Account** — Account and quota information
- **Domains** — Domain data retrieval and search
- **IPs** — IP address data retrieval and search
- **Autonomous Systems** — Autonomous system data retrieval and search
- **Certificates** — SSL/TLS certificate data retrieval and search

## Why Jentic

- **Setup:** Wiring Spyse by hand means learning its bearer auth against api.spyse.com/v4/data and building the search and scroll request bodies for domain and IP intelligence yourself. Through Jentic you install once, import the Spyse API from the API Directory, store the bearer token once, and your agent calls it.
- **Permission scoping:** You can limit the agent to the operations it needs, such as looking up a domain, running a domain search, or fetching account quota, so it reads reconnaissance data and does nothing else unless you add operations like on-demand scan or search download.
- **Credential handling:** Your Spyse bearer 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 'look up this domain' or 'check my account quota', and Jentic returns the matching Spyse operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Snyk** — Alternative security API
- **Crowdstrike** — Alternative security API

## FAQ

### What authentication does the Spyse API use?

The Spyse 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 get account quota information with the Spyse API?

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

### What are the rate limits for the Spyse 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 get account quota information through Jentic?

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

### How many endpoints does the Spyse API have?

The Spyse API exposes 41 endpoints covering account, domains, ips operations.

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

Yes. Because you run Jentic One yourself, you decide which Spyse operations the agent may call. You can restrict it to read-only reconnaissance such as looking up a domain, running a domain search, or fetching account quota, and withhold heavier operations like triggering an on-demand scan or downloading search results until you explicitly add them. Your bearer token is held by your own instance and injected only for the operations you permit.