AI AGENT STORE / SERVICES

WEB DATA & EXTRACTION · FOR AI AGENTS

Censys Platform

Look up observed internet assets, certificates and exposed services using API or MCP.

Censys provides maintained observations of internet-facing hosts, web properties and certificates. Agents can retrieve asset context for an inventory review or investigate a known indicator without operating their own internet-wide measurement system.

Your integration checklist

What you need from your owner
Create a Platform account and select the appropriate plan. Organization access requires the API Access role. Choose the organization whose entitlements and credits should be used.
Authentication
Connect to https://mcp.platform.censys.io/platform/mcp/ with OAuth or a personal access token. REST requests use Authorization: Bearer with a PAT and optionally X-Organization-ID; legacy Search credentials are a different interface.
Your first task
Retrieve a known asset from your inventory and compare observed services and timestamps with your current internal record.
Billing & payment
Free and Starter usage consumes platform credits, shared across applicable UI and API operations. Free API access is limited to host, certificate and web-property lookups; search and other endpoints depend on plan.
Agent payment support
Not verified. Programmatic usage does not establish autonomous checkout support.
Operational limits
Observations can be incomplete or older than the current asset state. A detected service or certificate does not establish exploitability or ownership. API/MCP access does not grant permission to change or probe third-party systems.

ORIGINAL AI AGENT STORE INTEGRATION PLAYBOOK

Attach observation time and identity confidence to each inventory finding

Editorial recommendation · Reviewed 2026-11-13

When to choose this service

Choose Censys when an investigation needs externally collected asset observations. Internal inventory remains necessary for resources that are private or not observed.

Internet-scale measurement infrastructure and historical asset records cannot be recreated by reasoning from an IP address. The service supplies evidence that still needs contextual validation.

Suggested workflow

  1. Start with the exact host, certificate fingerprint or web property in scope. Confirm the account and organization entitlements.
  2. Retrieve the record and preserve observation times, service details and identifiers. Compare them with the owner’s current inventory.
  3. Summarize discrepancies as findings to verify. Distinguish an old observation from a confirmed current exposure before requesting remediation.

Acceptance checks before real work

  • An empty lookup does not prove an asset is absent.
  • A shared certificate or IP does not uniquely identify an organization.
  • A free lookup entitlement does not imply search access.

If the workflow fails

For authorization errors, check PAT validity, organization and API role. For conflicting observations, inspect timestamps and asset identity before making a remediation recommendation.

Provider documentation

Explore services for adjacent needs

Continue building your toolkit