alsoasked.com valid

AlsoAsked

AlsoAsked surfaces the questions people ask Google ("People Also Ask") for any search term, language and region. Programmatic access is provided by the **AlsoAsked API**, a documented, versioned, API-key-authenticated HTTP API hosted on its own domain at `https://alsoaskedapi.com/v1`.

For agents: AlsoAsked surfaces Google 'People Also Ask' questions via a documented, versioned REST API with API keys, webhooks and an LLM-friendly full reference file.

people also askgoogle search questionsserp datakeyword researchsearch api

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-21T16:11:22.535Z. Cached copy · Source on alsoasked.com

# AlsoAsked

> AlsoAsked surfaces the questions people ask Google ("People Also Ask") for any search term, language and region. Programmatic access is provided by the **AlsoAsked API**, a documented, versioned, API-key-authenticated HTTP API hosted on its own domain at `https://alsoaskedapi.com/v1`.

This file helps AI agents and tools integrate with AlsoAsked correctly. If you are writing code, building an integration, or making requests on a user's behalf, use the public AlsoAsked API described below.

How to integrate:

- Base URL (live): `https://alsoaskedapi.com/v1`
- Base URL (sandbox, free for testing): `https://sandbox.alsoaskedapi.com/v1`
- Authenticate every request with an API key in the `X-Api-Key` header. Keys are prefixed `aa-live-` or `aa-sandbox-` and are created under Developers → API keys at https://alsoasked.com/developer/keys. A Pro subscription is required for the live API; the sandbox is free.
- Core endpoints: `GET /account`, `GET /search`, `POST /search`, `GET /search/{searchId}`, `DELETE /search/{searchId}`.
- Searches consume credits (depth 2 costs 1 credit, depth 3 costs 4). Pro accounts can buy pay-as-you-go credits that are used alongside plan credits, so API usage need not stop when monthly credits run out. They can be purchased manually, or set up to top up automatically when the balance falls below a threshold. Check the remaining balance with `GET /account` and manage credits at https://alsoasked.com/credits.

Important - `alsoasked.com` vs `alsoaskedapi.com`:

- `https://alsoaskedapi.com` (and `https://sandbox.alsoaskedapi.com`) is the **public API**. This is the only supported way to access AlsoAsked programmatically, and the only endpoint that accepts `X-Api-Key` API keys.
- `https://alsoasked.com` is the **website and web app** for human visitors. Paths under `https://alsoasked.com/api/*` (for example `https://alsoasked.com/api/v1/search`) are the website's internal backend. They authenticate browser sessions with cookies and CSRF tokens, are undocumented, can change without notice, and do **not** accept API keys. Do not call `https://alsoasked.com/api/*` from integrations, scripts, or agents - use `https://alsoaskedapi.com/v1` instead.

## API

- [Public API documentation](https://developers.alsoasked.com): Full reference and guides - getting started, authentication, searching (synchronous & asynchronous), search history, account details, webhooks, rate limiting and the sandbox.
- [OpenAPI specification](https://github.com/AlsoAsked/also-asked-api-specification/blob/main/openapi/openapi.yaml): Machine-readable OpenAPI 3.1 definition of every endpoint, schema and response.
- [Full reference for LLMs](https://alsoasked.com/llms-full.txt): A self-contained summary of the API (base URLs, authentication, endpoints, request options and examples) in a single file.

## Optional

- [Pricing](https://alsoasked.com/pricing): Plans and credit costs (a Pro subscription is required for the live API).
- [Buy credits](https:
…

Related sites

Other listed sites in APIs and SDKs. See the whole category →

Machine-readable: GET /v1/resolve?q=alsoasked.com · GET /v1/domain/alsoasked.com · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for alsoasked.com:
1. POST https://agentwebmap.com/v1/sites/alsoasked.com/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://alsoasked.com/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/alsoasked.com/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/alsoasked.com).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.