timzinin-com Ai Answer Change Alert API
The Ai Answer Change Alert API from timzinin-com — 1 operation(s) for ai answer change alert.
The Ai Answer Change Alert API from timzinin-com — 1 operation(s) for ai answer change alert.
Every API here is available over the APIs.io API and to AI agents over MCP.
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
find_apisBrowse and filter every API in the catalog.get_api_artifactsOne API's artifacts, grouped by type.get_openapiThe primary OpenAPI for this API.find_similar_apisAPIs that look like this one.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.curl "https://apis.io/api/v1/apis/timzinin-com:timzinin-com-ai-answer-change-alert-api"
curl "https://apis.io/api/v1/apis?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.
openapi: 3.2.0
info:
title: Zinin M2M Hub Ai Answer Change Alert API
description: Pay-per-call data & tool APIs
version: 1.0.0
x-guidance: 'Zinin M2M Hub — pay-per-call data & tool APIs for AI agents. Each POST /api/{slug} operation below is a distinct paid tool: call GET /api/{slug}/schema first for the exact input shape, then POST with a signed PAYMENT-SIGNATURE header (x402 v2, USDC — see x-payment-info per operation) or omit it to receive a 402 with full payment requirements in the PAYMENT-REQUIRED header. The same catalog is also available as MCP JSON-RPC tool bundles at POST /mcp/{bundle} — see GET /.well-known/x402 for the list of bundles.'
tags:
- name: Ai Answer Change Alert
paths:
/api/ai-answer-change-alert:
post:
summary: AI Answer Change Alert
description: Ask an LLM the queries that matter to you, compare each answer against its stored baseline and get told what changed — the answer itself and which domains it now cites or stopped citing. One row per query x model.
operationId: call_ai_answer_change_alert
x-payment-info:
price:
mode: fixed
currency: USD
amount: '0.100000'
protocols:
- x402: {}
network: eip155:8453
payTo: '0x409D32aD39C02BC9B23a8b2d447532ed801b12dE'
asset: '0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913'
requestBody:
required: true
content:
application/json:
schema:
title: AI Answer Change Alert input
type: object
schemaVersion: 1
properties:
queries:
title: Queries
type: array
description: The prompts a real user would ask (e.g. `best crm for small business`). Each query is run against every model in `models` below and compared against the previous run's stored answer for the same query × model × language — you are charged per query × model pair, not per query, whether or not the answer changed.
maxItems: 20
editor: stringList
prefill:
- best crm for small business
models:
title: Models
type: array
description: 'OpenRouter model IDs to check. Grounded options: `perplexity/sonar`, `openai/gpt-4o-mini:online`, `google/gemini-2.0-flash-001:online`. Every model you add multiplies the number of billed rows: rows = number of queries × number of models. With the limits on both fields, the maximum possible is 20 queries × 3 models = 60 rows.'
maxItems: 3
editor: stringList
prefill:
- perplexity/sonar
lang:
title: Language
type: string
description: Answer language (e.g. en, ru, tr).
editor: textfield
default: en
openrouterApiKey:
title: OpenRouter API key
type: string
description: 'Your OpenRouter API key (https://openrouter.ai/keys). Optional: without it the built-in key is used and the LLM cost is covered by the per-row price. Pass your own key to have tokens billed to your account instead, at cost.'
editor: textfield
isSecret: true
maxConcurrency:
title: Max concurrency
type: integer
description: Parallel LLM calls (kept low to respect rate limits and to bound how many LLM calls can be wasted — uncharged — if a run's spend limit is hit mid-run).
default: 1
minimum: 1
maximum: 3
required:
- queries
responses:
'200':
description: Actor run succeeded and payment settled
content:
application/json:
schema:
type: object
properties:
results:
type: array
items:
type: object
description: Actor output items — shape is actor-specific (varies per tool); see this operation's own requestBody schema/description for what the underlying actor produces.
meta:
type: object
properties:
run_ms:
type: integer
description: Actor run duration in milliseconds
item_count:
type: integer
description: len(results)
settled:
type: boolean
description: Whether the x402 payment was confirmed settled by the facilitator
transaction:
type:
- string
- 'null'
description: On-chain settlement transaction hash, null if unsettled
required:
- run_ms
- item_count
- settled
- transaction
required:
- results
- meta
'400':
description: Malformed PAYMENT-SIGNATURE header or request body
'402':
description: Payment required or invalid — see PAYMENT-REQUIRED header
'409':
description: Payment payload already used
'502':
description: Actor run failed
'504':
description: Actor run timed out
tags:
- Ai Answer Change Alert