---
title: "Search, crawling and extraction."
description: "A research pipeline finds relevant sources, retrieves permitted pages and turns evidence into structured fields. Each step needs its own scope and quality checks."
canonical: "https://altss.com/console/search-and-discovery"
last-updated: "2026-11-17"
---

# Search, crawling and extraction.

A research pipeline finds relevant sources, retrieves permitted pages and turns evidence into structured fields. Each step needs its own scope and quality checks.

Last modified: 2026-11-17

## Find the right evidence before extracting it

An acquisition researcher may begin with a sector and geography, then need official company pages, ownership disclosures and dated transaction announcements. Search relevance determines which sources deserve attention. Retrieval determines what was actually captured. Extraction determines what a source supports.

Treating those as separate steps makes a research result easier to review. A search snippet is a lead, a fetched page is a source, and an extracted field is a claim whose evidence needs to remain accessible. The workflow should retain those distinctions in its output.

## Web search API requirements

Define the question, entity type, permitted domains and relevant date window. Ask for the source URL, title, publication date when known and a reason for relevance. The existing anonymous Altss reader searches published Altss profiles; it is not a general web-search API.

[Public profile search API](https://altss.com/api/v1/public/openapi.json)

## Web crawling API requirements

Set the start URLs, permitted hostnames, page budget and required content types. Preserve the retrieval timestamp, final URL and retrieval outcome. A crawler must distinguish a successful capture from a blocked page, redirect or empty document; failed retrieval should never become an invented source.

## Data extraction API requirements

Specify field names, data types and evidence expectations before extraction. For a headquarters address, retain the exact organization and supporting text. For a funding event, retain the round and date rather than silently labeling a single round as total funding. Null and ambiguous are useful outcomes when a source is incomplete.

## A company-discovery workflow

### 1. Set the market boundary

Define the industry, geography, ownership criteria and exclusions. Distinguish an operating company from its parent, brand and investor.

### 2. Keep source-level evidence

Review relevant official pages and disclosures. Carry source URLs and dates alongside extracted fields, with an unresolved state where identity or coverage is uncertain.

### 3. Review the shortlist

Compare the companies against the original criteria. Preserve the reason each company qualified and the missing evidence that could change the decision.

## A source review record

Illustrative customer-owned output design, not a Console API response schema or a live company record.

```json
{
  "entity": {
    "name": "Example Manufacturing",
    "officialDomain": "example.com",
    "identityStatus": "needs_review"
  },
  "criterion": "Operates industrial automation facilities in the selected market",
  "evidence": [
    {
      "sourceUrl": "https://example.com/company",
      "capturedAt": null,
      "supports": "Operating activity requires review"
    }
  ],
  "unknowns": [
    "Ultimate ownership",
    "Group headquarters"
  ]
}
```

## Choose the available capability before funding

The separate Altss Console publishes authenticated REST and MCP interfaces and a catalog for bounded SEC financial research using public issuer filings. Follow its connection guide and current tool catalog for account eligibility, credential setup, scope, quotes and funding requirements. This does not grant private-company dossiers, contact enrichment or unrestricted graph access.

[Read the current Console catalog](https://console.altss.com/tools.json)

[Check Console pricing](https://console.altss.com/pricing)

## Next steps

- [Scope a search or extraction requirement](https://altss.com/contact)
- [Company and people identity](https://altss.com/console/enrichment)
- [Console documentation](https://altss.com/console/docs): Choose a protocol, authorize a credential and follow the quote-to-result contract.

[Discuss your workflow](https://altss.com/contact)

[Explore capabilities](https://altss.com/console/capabilities)

## Give your agents a defined job.

Start with the capability, its evidence requirements and the decision your team needs to make. Confirm the available tool and permitted use before execution.

[Read the connection guide](https://console.altss.com/connect)

[Discuss a requirement](https://altss.com/contact)

Canonical URL: https://altss.com/console/search-and-discovery

