Official vendor OpenAPI document · agent-readySecurityThreat Detectionbearer41 EndpointsREST
For Agents
Programmatically get account quota information, get domain details. Covers 41 operations with bearer authentication.
Use for: I need to account quota information, I want to domain details, Search for domains, Find all count domain search results
Not supported: Does not handle payments, communications, or crm - use for security only.
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.
Install Jentic One Beta
Connect the Spyse API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Spyse 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.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fspyse.com%2Fspyse" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fspyse.com%2Fspyse" | 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.
Capabilities
What an agent can do with Spyse API.
Get account quota information
Search domains
Count domain search results
Download domain search results
Scroll search domains
Trigger on-demand domain scan
Use Cases
Patterns agents use Spyse API for, with concrete tasks.
★ 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.
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.
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.
Search Jentic for 'get account quota information', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
41 endpoints — spyse is an internet assets search engine that provides comprehensive data on domains, ips, ssl certificates, autonomous systems, cves, and emails.
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
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
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
S
Spyse API
- AI-Aware (B+)69/100
87
Foundational Compliance63
Developer Experience & Jentic Compatibility53
AI-Readiness & Agent Experience94
Agent Usability60
Security100
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
87
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: ASignals: 4
97%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
100%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
50%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
63
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: B-Signals: 4
0%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
50%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
53
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: C-Signals: 4
61%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
100%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
50%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
60
Security
Trust, risk posture, and security compliance.
Grade: B-Signals: 1
60%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
100
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: A+Signals: 1
100%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
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 isolation
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.
Intent-based discovery
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
Alternatives and complements available in the Jentic catalogue.
Alternative
Snyk
Alternative security API
Choose Snyk when you need a different approach to security operations
FAQs
Specific to using Spyse API through Jentic.
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.
GET STARTED