API Overview
Start here to learn the flow, the available lanes, and how to keep requests focused.
Overview
Intelfetch is designed around a simple idea: begin with one clear clue, choose the closest lane, and refine only when needed.
The interface exposes three practical entry points:
- Username
- News
Each lane follows the same pattern:
- Enter the smallest useful input.
- Add context only if it reduces noise.
- Review the first result set.
- Narrow the input and try again if needed.
How to work with it
The best results come from short, exact inputs. If the subject is already specific, keep it that way. If the subject is broad, add one extra constraint at a time rather than changing everything at once.
Response style
Every run returns a structured result with:
- A normalized list of findings
- A source name for each finding
- A timestamp for traceability
- Optional typed sections when the lane produces structured output
Authentication
All requests use a Bearer token in the Authorization header.
If you are testing from the UI, the docs and examples should point at the same backend base URL your environment provides.
Environment
Base URL: https://test.intelfetch.dev/api/v1
The site uses the environment value when it is available, so the docs stay aligned with the deployment you are actually running.
Quick start
- Pick one lane.
- Use one clue.
- Read the summary first.
- Open only the items that look relevant.