Seven OSINT Tools, One Developer API

Osintly now gives developers direct API access to seven focused OSINT tools.

You can resolve a gaming identity, inspect public profile signals, enrich a vehicle identifier, or retrieve a complete account snapshot without maintaining a separate integration for every provider. Each tool also has a hosted demo, so you can understand the workflow before writing code.

The Tools API starts at €19 per month. It uses one authentication model, one base URL, normalized JSON responses, and route-level cost discovery.

Seven tools you can test before you integrate

The current catalog covers six gaming platforms and one vehicle intelligence workflow.

Browse the full hosted Tools catalog or start with the Tools API overview.

From hosted demo to API request

The hosted tools are useful for manual research and for understanding the inputs and results. The API exposes the same focused workflows for products, internal systems, enrichment pipelines, bots, and automated investigations.

Every endpoint lives under:

https://api.osint.ly/tools

Authenticate with an Osintly API key:

curl -X GET "https://api.osint.ly/tools" \
  -H "Authorization: Bearer $OSINTLY_API_KEY"

Tools share the same bearer authentication, plan checks, rate-limit behavior, and account-level usage system. Read the authentication guide before your first request.

Most tools follow the same pattern:

1. Validate and normalize the submitted identifier with /search.

2. Call a focused route when you only need one signal group.

3. Call /all when you want the main collectors in one response.

4. Add save: true when you need to retrieve the result later.

The validation route does not contact the upstream provider and does not consume core-search credits. Provider-backed routes return the actual enrichment data.

Epic Games shows how deep one tool can go

The Epic Games API is more than a display-name resolver.

It accepts nine canonical identifier types:

Aliases such as epic, creator, psn, steam, xbox, and nintendo are normalized automatically.

Start by validating an identifier:

curl -X POST "https://api.osint.ly/tools/epic-games/search" \
  -H "Authorization: Bearer $OSINTLY_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"value":"some-player","type":"epic_display_name"}'

That request checks and normalizes the input without calling Epic or using credits.

For provider-backed enrichment, choose the smallest route that fits the job:

When you need the main collectors together, use /all:

curl -X POST "https://api.osint.ly/tools/epic-games/all" \
  -H "Authorization: Bearer $OSINTLY_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"value":"some-player","type":"epic_display_name","save":true}'

The route costs two core-search credits and charges once for the combined result. With save: true, the response includes meta.savedResult.id, which you can use to retrieve the result later.

The complete route contract, identifier aliases, response behavior, and Creator profile fields are documented in the Epic Games reference.

You can also test the workflow in the hosted Epic Games demo.

Ask the API what a route costs

You do not have to hardcode tool costs or rely on a pricing table that can become stale.

Each tool exposes a /costs endpoint:

curl -X GET "https://api.osint.ly/tools/epic-games/costs" \
  -H "Authorization: Bearer $OSINTLY_API_KEY"

The response lists the default price and every route pattern with its method, cost type, and quantity. Free validation or detail routes report a quantity of zero. Paid collector routes report their core-search credit cost.

Here, free means zero core-search credit cost after Tools API access is enabled. Tool execution still requires a paid API subscription.

This lets your application check costs before execution, choose a focused route instead of /all, or show expected usage to the user.

Save results without building another storage flow

The /all route can save a synchronous result when you send save: true. A saved response returns a result ID.

Retrieve it later with:

curl -X GET "https://api.osint.ly/tools/results/<result_id>" \
  -H "Authorization: Bearer $OSINTLY_API_KEY"

Saved results are scoped to the API key and creator that stored them. Another account or key cannot retrieve them.

This is useful when an enrichment needs to be reviewed later, attached to an internal case, or passed to a downstream process without immediately creating a full Osintly search.

Pricing for builders and production workloads

Every API subscription currently includes Tools access.

The Builder plan starts at €19 per month and includes:

Growth is available at €49 per month for 3,000 monthly requests, higher rate limits, five API keys, and priority support. Scale is available at €249 per month for 15,000 monthly requests, 15 API keys, and higher production capacity.

Review the live limits and current plan details on the API pricing page. For larger or specialized workloads, contact the Osintly team.

Tools API or Search API?

Use the Tools API when you know the observable type and want one direct enrichment response. It has lower workflow overhead and lets you target a specific signal group.

Use the Search API when you need Osintly to coordinate a full investigation. The Search API can:

Both APIs use the same account-level authentication and usage model. You can start with a direct tool today and add full search orchestration when your product needs it.

Compare the two surfaces in the API introduction. Then review the quick start, SSE reference, and webhook guide.

Public data still has limits

Tool results depend on what the upstream platform exposes publicly and whether the source is available at request time.

A private gaming profile can return partial data. An identifier can be valid even when a provider temporarily returns no enrichment. Combined /all responses may include partialErrors when a secondary collector fails, while still returning the data that was available.

The Vehicle History Finder does not return personal owner data. For French vehicles, full official history remains available through official services such as HistoVec or ANTS.

These boundaries are part of the API contract. Applications should preserve source context, handle null fields and partial errors, and avoid treating an automated result as a final judgment.

Read Osintly's Terms of Use and Ethics Policy before deploying an integration.

Start building

1. Explore the hosted Tools catalog.

2. Read the Tools API overview.

3. Review API plans and capacity.

4. Create and secure an API key using the authentication guide.

5. Make your first request with the quick start.

If you are adding OSINT enrichment to a product, analyst workspace, internal tool, or automated workflow, visit the developer overview or talk to our team.