Wikipedia Article Lookup by URL or Keyword: one-request API, MCP and n8n
One record per Wikipedia article with summary, description, categories, images, Wikidata ID, coordinates, revision metadata and optional full text, sections, links, references and pageviews.
Server mode on Also answers single HTTP requests with the results in the response. Call it as an API.
Fastest route, one HTTP request (results in the response):
curl -H "Authorization: Bearer $APIFY_TOKEN" \
"https://vexaloom-labs--wikipedia-article-lookup-by-url-or-keyword.apify.actor/?articleTitles=Ada%20Lovelace" One click, signs in with Apify on first use:
Any other client, one command (writes the config for 25+ agents, including Windsurf, Zed, Cline and Goose):
npx add-mcp "https://mcp.apify.com/?tools=fetch-actor-details,vexaloom-labs/wikipedia-article-lookup-by-url-or-keyword" --name wikipedia-article-lookup-by-url-or-keyword Every file on this page is generated from the Actor's published schema: 58 of 58 checks pass (validated, not run)
- MCP configs: 7 of 7 (Uses Apify's hosted MCP endpoint over HTTPS; The tools parameter lists exactly the chosen Actors as owner/name; JSON configs parse and use the client's top-level key and the same URL; Codex TOML has a [mcp_servers.<name>] table with url and bearer_token_env_var; CLI commands quote the same URL and use the streamable HTTP transport; One-click install links decode back to the same URL and carry no token; Only placeholders, no real token)
- n8n workflow: 11 of 11 (It has a nodes array and a connections object; Every node has a name, type, typeVersion, position and parameters; Node names are unique; Every node type is a known n8n core node (or the Apify node); Every node uses a typeVersion that n8n ships; Every connection points at an existing node; At least one trigger starts the workflow; Every working node is reachable from a trigger; Apify calls use POST and a credential for the token; Actor input matches the Actor's published input schema; No token or credential value is embedded)
- long-run workflow: 11 of 11 (It has a nodes array and a connections object; Every node has a name, type, typeVersion, position and parameters; Node names are unique; Every node type is a known n8n core node (or the Apify node); Every node uses a typeVersion that n8n ships; Every connection points at an existing node; At least one trigger starts the workflow; Every working node is reachable from a trigger; Apify calls use POST and a credential for the token; Actor input matches the Actor's published input schema; No token or credential value is embedded)
- example input: 5 of 5 (The schema has no required fields; Every input key exists in the published input schema; Every value has the type the schema declares; Every choice field uses one of its published options; Numbers respect the published minimum and maximum)
- code snippets: 4 of 4 (curl calls the documented run-sync-get-dataset-items endpoint for this Actor; Python (apify-client 3.x typed Run) and JavaScript use the official apify-client call() then read the run's dataset; Multi-line shell commands continue every line with a backslash; Token read from APIFY_TOKEN, none embedded)
- SKILL.md: 13 of 13 (SKILL.md starts with YAML front matter; name is 1-64 lowercase letters, digits and single hyphens; name matches the skill folder name; description is present, at most 1024 characters and has no angle brackets; front matter uses only spec fields; compatibility is at most 500 characters; body has instructions; field descriptions end on whole sentences; no credential values are embedded; the token is read from APIFY_TOKEN; the run command calls this Actor's run-sync endpoint; the example input is valid JSON; the example input matches the published input schema)
- server snippets: 7 of 7 (Server host is a resolvable apify.actor name (DNS label of 63 characters or fewer); The Actor publishes an OpenAPI 3 schema for its server; Multi-line shell commands continue every line with a backslash; Every example parameter is declared in the server schema; The example stays inside the per-request caps; Slashes in values are encoded (the platform collapses // in request paths); Token comes from APIFY_TOKEN, none embedded)
What a run costs
Every run pays a start fee plus a price per result. On the Free plan this Actor's start fee is $0.40 (the start event, $0.10 per GB, times its default 4 GB of memory), $0.12 on Business; results cost $0.99 per 1,000 results (pay per event). Checked 2026-11-12.
| Results in one run | Start | Results | Run total |
|---|---|---|---|
| 10 | $0.40 | $0.010 | $0.41 |
| 100 | $0.40 | $0.10 | $0.50 |
| 1,000 | $0.40 | $0.99 | $1.39 |
Plus Apify platform usage for the run, which the caller pays. A smaller memory setting lowers the start fee if the Actor still finishes. Prices can change; the Store pricing tab is the source of truth.
MCP config
One URL works in every client: https://mcp.apify.com/?tools=fetch-actor-details,vexaloom-labs/wikipedia-article-lookup-by-url-or-keyword. It exposes this Actor as a tool, plus fetch-actor-details so the agent can read the input schema before calling it. Pick your client:
Claude Code configterminal or .mcp.json
claude mcp add --transport http wikipedia-article-lookup-by-url-or-keyword "https://mcp.apify.com/?tools=fetch-actor-details,vexaloom-labs/wikipedia-article-lookup-by-url-or-keyword" Run the command in your project folder. Add --scope user to make it available in every project. Full Claude Code setup
Claude Desktop configclaude_desktop_config.json
{
"mcpServers": {
"wikipedia-article-lookup-by-url-or-keyword": {
"command": "npx",
"args": [
"-y",
"@apify/actors-mcp-server",
"--tools",
"fetch-actor-details,vexaloom-labs/wikipedia-article-lookup-by-url-or-keyword"
],
"env": {
"APIFY_TOKEN": "YOUR_APIFY_TOKEN"
}
}
}
} Easiest: open Customize, then Connectors, choose Add custom connector, paste the server URL (the ChatGPT tab shows it on its own) and sign in to Apify. Full Claude Desktop setup
Cursor config~/.cursor/mcp.json
{
"mcpServers": {
"wikipedia-article-lookup-by-url-or-keyword": {
"url": "https://mcp.apify.com/?tools=fetch-actor-details,vexaloom-labs/wikipedia-article-lookup-by-url-or-keyword",
"headers": {
"Authorization": "Bearer ${env:APIFY_TOKEN}"
}
}
}
} Save as ~/.cursor/mcp.json for every project, or .cursor/mcp.json for one project. Merge with servers you already have. Full Cursor setup
VS Code config.vscode/mcp.json
{
"inputs": [
{
"type": "promptString",
"id": "apify-token",
"description": "Apify API token",
"password": true
}
],
"servers": {
"wikipedia-article-lookup-by-url-or-keyword": {
"type": "http",
"url": "https://mcp.apify.com/?tools=fetch-actor-details,vexaloom-labs/wikipedia-article-lookup-by-url-or-keyword",
"headers": {
"Authorization": "Bearer ${input:apify-token}"
}
}
}
} Save as .vscode/mcp.json in your workspace. Full VS Code setup
ChatGPT configPlugins > Add custom MCP server
https://mcp.apify.com/?tools=fetch-actor-details,vexaloom-labs/wikipedia-article-lookup-by-url-or-keyword In ChatGPT on the web, open Plugins, select + and choose Add custom MCP server. Full ChatGPT setup
Codex CLI config~/.codex/config.toml
[mcp_servers.wikipedia-article-lookup-by-url-or-keyword]
url = "https://mcp.apify.com/?tools=fetch-actor-details,vexaloom-labs/wikipedia-article-lookup-by-url-or-keyword"
bearer_token_env_var = "APIFY_TOKEN" Add the block to ~/.codex/config.toml, or .codex/config.toml in a project. Full Codex CLI setup
Gemini CLI configterminal (writes ~/.gemini/settings.json)
gemini mcp add -t http -s user -H "Authorization: Bearer $APIFY_TOKEN" wikipedia-article-lookup-by-url-or-keyword "https://mcp.apify.com/?tools=fetch-actor-details,vexaloom-labs/wikipedia-article-lookup-by-url-or-keyword" Export APIFY_TOKEN first: the shell expands it and Gemini CLI saves the header, token included, in plain text in ~/.gemini/settings.json (keep that file private). In PowerShell write $env:APIFY_TOKEN instead of $APIFY_TOKEN. Drop -s user to save it in the project's .gemini/settings.json. Full Gemini CLI setup
n8n AI Agent configMCP Client Tool node
https://mcp.apify.com/?tools=fetch-actor-details,vexaloom-labs/wikipedia-article-lookup-by-url-or-keyword Add an AI Agent node, then attach an MCP Client Tool node to its tool input. Full n8n AI Agent setup
Tools your agent gets
Listed by Apify's MCP server 0.21.5 for this exact URL on 2026-11-11 (a tools/list call; nothing was run).
fetch-actor-detailsreads the input schemavexaloom-labs--wikipedia-article-lookup-by-url-or-keywordsends one request to the Actor's server
This Actor has a server interface, so its tool sends one HTTP request instead of starting a batch run. For batch runs add call-actor to the tools list: https://mcp.apify.com/?tools=fetch-actor-details,call-actor,vexaloom-labs/wikipedia-article-lookup-by-url-or-keyword
Call it as an API: one request, one answer
Server mode is switched on for this Actor (single-tenant, checked 2026-11-12 through the Apify API). Instead of starting a run and reading a dataset, send the input as an HTTP request to https://vexaloom-labs--wikipedia-article-lookup-by-url-or-keyword.apify.actor/ and the results come back in the response. The request starts a run in your own Apify account, billed at the Actor's normal price.
Send one lookup and get the results back in the response. It takes the same input as a normal run: query parameters with GET, or a JSON body with POST. At most 20 results and 240 seconds per request; start a normal run for bigger jobs. Requests run in your own Apify account at the Actor's normal price.
From the Actor's published server schema.
curl (GET)
curl -H "Authorization: Bearer $APIFY_TOKEN" \
"https://vexaloom-labs--wikipedia-article-lookup-by-url-or-keyword.apify.actor/?articleTitles=Ada%20Lovelace" curl (POST)
curl -X POST "https://vexaloom-labs--wikipedia-article-lookup-by-url-or-keyword.apify.actor/" \
-H "Authorization: Bearer $APIFY_TOKEN" \
-H "Content-Type: application/json" \
-d '{"articleTitles":["Ada Lovelace"]}' JavaScript
// Node 18+ or any runtime with fetch. One request = one lookup; results come back in the response.
const response = await fetch("https://vexaloom-labs--wikipedia-article-lookup-by-url-or-keyword.apify.actor/", {
method: "POST",
headers: { Authorization: `Bearer ${process.env.APIFY_TOKEN}`, "Content-Type": "application/json" },
body: JSON.stringify({
"articleTitles": [
"Ada Lovelace"
]
}),
});
if (!response.ok) throw new Error(`${response.status}: ${await response.text()}`);
const items = await response.json();
console.log(items.length, items[0]); Python
import os
import requests
# One request = one lookup; results come back in the response.
response = requests.post(
"https://vexaloom-labs--wikipedia-article-lookup-by-url-or-keyword.apify.actor/",
headers={"Authorization": f"Bearer {os.environ['APIFY_TOKEN']}"},
json={
"articleTitles": [
"Ada Lovelace",
],
},
timeout=300,
)
response.raise_for_status()
items = response.json()
print(len(items), items[:1]) Parameters and per-request caps
| Parameter | Type | Cap |
|---|---|---|
articleUrls | array | 10 values |
articleTitles | array | 10 values |
searchQueries | array | 3 values |
maxArticlesPerQuery | integer | max 10 |
categoryNames | array | 2 values |
maxArticlesPerCategory | integer | max 20 |
language | string (374 options) | none |
maxItems | integer | max 20 |
includeFullContent | boolean | none |
includeSections | boolean | none |
includeExternalLinks | boolean | none |
includeLinks | boolean | none |
includeReferences | boolean | none |
includePageviews | boolean | none |
pageviewsGranularity | string (2 options) | none |
pageviewsPeriods | integer | max 365 |
Response codes
- 200
- The results as a JSON array (at most 20). They are also saved to the run's dataset and billed per result, like a normal run.
- 400
- Invalid, missing or unknown input fields. Nothing ran.
- 422
- The Actor could not complete this request (for example, nothing matches). No results were delivered.
- 500
- Unexpected failure. Safe to retry.
- 504
- The request used up its 240 s budget. The results found so far are in partialItems.
Example response
The first record of the example response in the Actor's own server schema, long values shortened. Nothing was run for this page.
[
{
"title": "Ada Lovelace",
"url": "https://en.wikipedia.org/wiki/Ada_Lovelace",
"canonicalUrl": "https://en.wikipedia.org/wiki/Ada_Lovelace",
"displayTitle": "Ada Lovelace",
"summary": "Augusta Ada King, Countess of Lovelace (née Byron; 10 December 1815 – 27 November 1852), also known as Ada Lovelace, was an English mathematician and writer ...",
"description": "English mathematician (1815–1852)",
"language": "en",
"pageId": 974,
"wikidataId": "Q7259",
"lastModified": "2026-11-06T19:02:23Z",
"categories": [
"1815 births",
"1852 deaths",
"19th-century British women mathematicians"
],
"thumbnail": {
"source": "https://upload.wikimedia.org/wikipedia/commons/4/4c/Ada_Lovelace_daguerreotype_by_Antoine_Claudet_1843_-_cropped.png",
"width": 957,
"height": 1239
},
"images": [
"https://upload.wikimedia.org/wikipedia/commons/9/9e/Square_root_of_x.svg",
"https://upload.wikimedia.org/wikipedia/commons/a/aa/Newton%27s_reflecting_telescope.jpg",
"https://upload.wikimedia.org/wikipedia/commons/e/e7/Miniature_of_Ada_Byron.jpg"
],
"languageCount": 113,
"availableLanguages": [
"af",
"an",
"ar"
],
"revisionId": 1384127064,
"lastEditor": "Vitorperrut555",
"lastEditComment": "Copying from [[Category:British women computer scientists]] to [[Category:British computer scientists]] using [[c:Help:Cat-a-lot|Cat-a-lot]]",
"revisionSize": 98391,
"wordCount": 476,
"requestedTitle": "Ada Lovelace",
"requestedTitles": [
"Ada Lovelace"
],
"scrapedAt": "2026-11-10T15:33:49.311825+00:00"
}
] Download the OpenAPI file Open the Actor on Apify
The OpenAPI file is the Actor's published schema with the server URL and bearer auth filled in, so tools that import OpenAPI (custom GPT actions, Postman, API client generators) can call it directly.
n8n workflow
A manual and a daily trigger call the Actor through the HTTP Request node with your Apify token, then hand each record to the destination you pick. The Actor input sits in the request body, already filled with the example below.
- Run by hand
- Every day
- Run Apify Actor
n8n workflowwikipedia-article-lookup-by-url-or-keyword.n8n.json
{
"name": "Wikipedia Article Lookup by URL or Keyword to n8n only",
"nodes": [
{
"id": "21e6c79a-743e-4be6-ab6c-4d3fae63b34b",
"name": "Run by hand",
"type": "n8n-nodes-base.manualTrigger",
"typeVersion": 1,
"position": [
0,
0
],
"parameters": {}
},
{
"id": "3da0ad7a-b6d6-4ea4-aec0-fe0df9a6bc4b",
"name": "Every day",
"type": "n8n-nodes-base.scheduleTrigger",
"typeVersion": 1.2,
"position": [
0,
200
],
"parameters": {
"rule": {
"interval": [
{
"triggerAtHour": 8
}
]
}
},
"notes": "Activate the workflow to run on this schedule."
},
{
"id": "cd8d6a56-53e9-4821-a91f-2374ab107dcb",
"name": "Run Apify Actor",
"type": "n8n-nodes-base.httpRequest",
"typeVersion": 4.2,
"position": [
260,
100
],
"parameters": {
"method": "POST",
"url": "https://api.apify.com/v2/actors/vexaloom-labs~wikipedia-article-lookup-by-url-or-keyword/run-sync-get-dataset-items",
"authentication": "genericCredentialType",
"genericAuthType": "httpHeaderAuth",
"sendBody": true,
"specifyBody": "json",
"jsonBody": "{\n \"articleUrls\": [\n \"https://en.wikipedia.org/wiki/Python_(programming_language)\"\n ],\n \"maxArticlesPerQuery\": 5,\n \"maxArticlesPerCategory\": 20,\n \"language\": \"en\",\n \"maxItems\": 100,\n \"includeFullContent\": false,\n \"includeSections\": false,\n \"includeExternalLinks\": false,\n \"includeLinks\": false,\n \"includeReferences\": false,\n \"includePageviews\": false,\n \"pageviewsGranularity\": \"monthly\",\n \"pageviewsPeriods\": 12\n}",
"options": {
"timeout": 310000
}
},
"notes": "Actor: vexaloom-labs/wikipedia-article-lookup-by-url-or-keyword. Select a Header Auth credential: name Authorization, value Bearer + your Apify token. Edit the JSON body to change the input.",
"notesInFlow": false
},
{
"id": "5a0a5c32-629d-450c-a6d4-5431b066e267",
"name": "Setup",
"type": "n8n-nodes-base.stickyNote",
"typeVersion": 1,
"position": [
0,
-370
],
"parameters": {
"content": "## Wikipedia Article Lookup by URL or Keyword\n\nSource: [vexaloom-labs/wikipedia-article-lookup-by-url-or-keyword](https://apify.com/vexaloom-labs/wikipedia-article-lookup-by-url-or-keyword) on Apify.\n\n1. In **Run Apify Actor**, create a Header Auth credential: name `Authorization`, value `Bearer YOUR_APIFY_TOKEN` with your token.\n2. Click **Execute workflow**. Each record arrives as one n8n item.\n3. Edit the JSON body of **Run Apify Actor** to change the input.\n\nGenerated by recipeforagents.com. Validated, not executed: runs are billed to your Apify account.",
"height": 340,
"width": 460,
"color": 6
}
}
],
"connections": {
"Run by hand": {
"main": [
[
{
"node": "Run Apify Actor",
"type": "main",
"index": 0
}
]
]
},
"Every day": {
"main": [
[
{
"node": "Run Apify Actor",
"type": "main",
"index": 0
}
]
]
}
},
"pinData": {},
"active": false,
"settings": {
"executionOrder": "v1"
},
"meta": {
"templateCredsSetupCompleted": false
},
"tags": []
} Import with Workflows, Import from file, or paste into the canvas. Credentials are not included: you select them after import.
All 7 destination variants pass the same checks at build time. Built-in nodes only, at versions n8n has shipped since 1.80: they import on n8n Cloud and older self-hosted instances without community nodes. Prefer Apify's own node? The verified community node @apify/n8n-nodes-apify runs the same Actor with OAuth sign-in on n8n Cloud.
Runs longer than 5 minutes? The synchronous endpoint answers HTTP 408 after 300 seconds. The long-run variant starts the run, checks it every minute until it ends, then reads its dataset (HTTP Request, If and Stop and Error nodes only).
Download the long-run workflow11 of 11 checks pass, not executed
Call it from code
Run the Actor from a script or your own agent framework with the Apify API. The call waits for the run to finish and returns the records; for a single lookup the server request above is faster. The input is the example below.
curl
curl -X POST "https://api.apify.com/v2/actors/vexaloom-labs~wikipedia-article-lookup-by-url-or-keyword/run-sync-get-dataset-items" \
-H "Authorization: Bearer $APIFY_TOKEN" \
-H "Content-Type: application/json" \
-d '{"articleUrls":["https://en.wikipedia.org/wiki/Python_(programming_language)"],"maxArticlesPerQuery":5,"maxArticlesPerCategory":20,"language":"en","maxItems":100,"includeFullContent":false,"includeSections":false,"includeExternalLinks":false,"includeLinks":false,"includeReferences":false,"includePageviews":false,"pageviewsGranularity":"monthly","pageviewsPeriods":12}' Install: pip install "apify-client>=3"
Python
import os
from apify_client import ApifyClient
client = ApifyClient(os.environ["APIFY_TOKEN"])
run_input = {
"articleUrls": [
"https://en.wikipedia.org/wiki/Python_(programming_language)",
],
"maxArticlesPerQuery": 5,
"maxArticlesPerCategory": 20,
"language": "en",
"maxItems": 100,
"includeFullContent": False,
"includeSections": False,
"includeExternalLinks": False,
"includeLinks": False,
"includeReferences": False,
"includePageviews": False,
"pageviewsGranularity": "monthly",
"pageviewsPeriods": 12,
}
run = client.actor("vexaloom-labs/wikipedia-article-lookup-by-url-or-keyword").call(run_input=run_input)
if run is None:
raise RuntimeError("The Actor run could not be started")
print(run.status, "dataset", run.default_dataset_id)
for item in client.dataset(run.default_dataset_id).iterate_items():
print(item) Install: npm install apify-client
JavaScript
import { ApifyClient } from "apify-client";
const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const input = {
"articleUrls": [
"https://en.wikipedia.org/wiki/Python_(programming_language)"
],
"maxArticlesPerQuery": 5,
"maxArticlesPerCategory": 20,
"language": "en",
"maxItems": 100,
"includeFullContent": false,
"includeSections": false,
"includeExternalLinks": false,
"includeLinks": false,
"includeReferences": false,
"includePageviews": false,
"pageviewsGranularity": "monthly",
"pageviewsPeriods": 12
};
const run = await client.actor("vexaloom-labs/wikipedia-article-lookup-by-url-or-keyword").call(input);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items.length, items[0]); Example input
These values come from the Actor's Store prefill and required defaults. Change the search, URL or limit before your first run.
Actor inputinput.json
{
"articleUrls": [
"https://en.wikipedia.org/wiki/Python_(programming_language)"
],
"maxArticlesPerQuery": 5,
"maxArticlesPerCategory": 20,
"language": "en",
"maxItems": 100,
"includeFullContent": false,
"includeSections": false,
"includeExternalLinks": false,
"includeLinks": false,
"includeReferences": false,
"includePageviews": false,
"pageviewsGranularity": "monthly",
"pageviewsPeriods": 12
} | Field | Type | What it does |
|---|---|---|
articleUrls | array | Wikipedia article URLs to look up. Works with desktop, mobile and index.php URLs, and with any language edition. |
maxArticlesPerQuery | integer | Maximum search results to fetch for each query (1-500). |
maxArticlesPerCategory | integer | Maximum category members to fetch for each category (1-500). |
language | string (374 options) | Wikipedia language edition for titles, searches and categories. URL lookups use the language in each URL instead. |
maxItems | integer | Hard cap on total article records emitted across all modes. |
includeFullContent | boolean | Add the complete article body as plain text in fullText (not only the lead summary). |
includeSections | boolean | Add the article's heading outline (title, level, anchor) in sections. |
includeExternalLinks | boolean | Add the outbound external URLs cited or listed by the article in externalLinks. |
includeLinks | boolean | Add the titles of other Wikipedia articles linked from the article in links. |
includeReferences | boolean | Add the number of inline citations in referencesCount. |
includePageviews | boolean | Add a pageview series and total in pageviews, from Wikimedia's pageview API. |
pageviewsGranularity | string (2 options) | Monthly or daily pageview points. Used when Include pageviews is on. |
pageviewsPeriods | integer | Number of pageview periods to return: 1-12 months for monthly, or 1-365 days for daily. |
3 more optional fields on the Store input tab.
What your agent receives
Each run returns a list of records. The Actor publishes 39 fields, starting with title, canonicalUrl, displayTitle, summary.
| Field | What it holds | Format |
|---|---|---|
title | Title | text |
url | URL | link |
canonicalUrl | Canonical article URL (same as url unless the API reports a different canonical form) | string |
displayTitle | Title as displayed by Wikipedia | string |
summary | Lead-section plain-text extract | string |
description | Description | text |
language | Lang | text |
pageId | Page ID | number |
wikidataId | Linked Wikidata entity ID, e.g. Q937 | string |
wordCount | Words | number |
29 more fields
| Field | What it holds | Format |
|---|---|---|
categories | Article categories without the Category: prefix | array |
thumbnail | Lead image thumbnail {source, width, height} | object |
originalImage | Original lead image {source, width, height} | object |
images | Viewable image URLs from the article body | array |
coordinates | Geographic coordinates {latitude, longitude} when present | object |
languageCount | Number of other language editions | integer |
availableLanguages | Language codes of other editions | array |
lastModified | ISO 8601 last-edit timestamp | string |
revisionId | Latest revision ID | integer |
lastEditor | User who made the latest revision | string |
lastEditComment | Latest revision comment | string |
revisionSize | Latest revision size in bytes | integer |
isDisambiguation | True for disambiguation pages | boolean |
redirectedFrom | Input title that redirected to this article | string |
fullText | Complete article body as plain text | string |
sections | Section outline [{title, level, anchor}] | array |
externalLinks | Outbound external URLs | array |
links | Titles of linked Wikipedia articles | array |
referencesCount | Number of inline citations | integer |
pageviews | Pageview series {granularity, start, end, total, points} | object |
searchQuery | First search query that matched this article | string |
searchRank | One-based rank in that search | integer |
searchSnippet | Plain-text search-result snippet | string |
requestedTitle | Title input that resolved to this article | string |
requestedTitles | All title inputs that resolved here | array |
requestedUrls | All URL inputs that resolved here | array |
matchedSearchQueries | All search queries that matched here | array |
sourceCategory | Category that produced this record, if any | string |
scrapedAt | ISO 8601 scrape timestamp | string |
Agent skill
A SKILL.md in the open Agent Skills format. It teaches Claude Code, Codex and other skill-aware agents when to call this Actor, how to build the input and how to read the result, using the API directly.
SKILL.mdwikipedia-article-lookup-by-url-or-keyword/SKILL.md
---
name: wikipedia-article-lookup-by-url-or-keyword
description: "One record per Wikipedia article with summary, description, categories, images, Wikidata ID, coordinates, revision metadata and optional full text, sections, links, references and pageviews. Runs the Apify Actor vexaloom-labs/wikipedia-article-lookup-by-url-or-keyword. Use when the user needs Wikipedia data with fields such as title, url, canonicalUrl, displayTitle, summary, description and an Apify token is available."
compatibility: "Needs network access, curl, and an APIFY_TOKEN environment variable. Runs are billed to the token owner's Apify account."
metadata:
actor: "vexaloom-labs/wikipedia-article-lookup-by-url-or-keyword"
store-url: "https://apify.com/vexaloom-labs/wikipedia-article-lookup-by-url-or-keyword"
---
# Wikipedia Article Lookup by URL or Keyword
Use this skill to fetch Wikipedia data with the Apify Actor `vexaloom-labs/wikipedia-article-lookup-by-url-or-keyword` and work with the returned rows.
## Before running
1. Check that `APIFY_TOKEN` is set in the environment. Never print it or write it to a file.
2. Build `input.json` from the user's request using the fields below. Keep limits small for a first run.
3. Confirm the search terms or URLs with the user if the request is ambiguous.
## Input fields
| Field | Type | Meaning |
| --- | --- | --- |
| `articleUrls` | array | Wikipedia article URLs to look up. Works with desktop, mobile and index.php URLs, and with any language edition. |
| `maxArticlesPerQuery` | integer | Maximum search results to fetch for each query (1-500). |
| `maxArticlesPerCategory` | integer | Maximum category members to fetch for each category (1-500). |
| `language` | string | Wikipedia language edition for titles, searches and categories. URL lookups use the language in each URL instead. |
| `maxItems` | integer | Hard cap on total article records emitted across all modes. |
| `includeFullContent` | boolean | Add the complete article body as plain text in fullText (not only the lead summary). |
| `includeSections` | boolean | Add the article's heading outline (title, level, anchor) in sections. |
| `includeExternalLinks` | boolean | Add the outbound external URLs cited or listed by the article in externalLinks. |
| `includeLinks` | boolean | Add the titles of other Wikipedia articles linked from the article in links. |
| `includeReferences` | boolean | Add the number of inline citations in referencesCount. |
| `includePageviews` | boolean | Add a pageview series and total in pageviews, from Wikimedia's pageview API. |
| `pageviewsGranularity` | one of `monthly`, `daily` | Monthly or daily pageview points. Used when Include pageviews is on. |
| `pageviewsPeriods` | integer | Number of pageview periods to return: 1-12 months for monthly, or 1-365 days for daily. |
Example `input.json` (the Actor's published prefill):
```json
{
"articleUrls": [
"https://en.wikipedia.org/wiki/Python_(programming_language)"
],
"maxArticlesPerQuery": 5,
"maxArticlesPerCategory": 20,
"language": "en",
"maxItems": 100,
"includeFullContent": false,
"includeSections": false,
"includeExternalLinks": false,
"includeLinks": false,
"includeReferences": false,
"includePageviews": false,
"pageviewsGranularity": "monthly",
"pageviewsPeriods": 12
}
```
## Run
```bash
curl -sS -X POST "https://api.apify.com/v2/acts/vexaloom-labs~wikipedia-article-lookup-by-url-or-keyword/run-sync-get-dataset-items" \
-H "Authorization: Bearer $APIFY_TOKEN" \
-H "Content-Type: application/json" \
-d @input.json > results.json
```
The call waits for the run to finish and returns the dataset items as a JSON array. If the run needs more than 300 seconds the API answers with HTTP 408; then start the run with `POST /v2/acts/vexaloom-labs~wikipedia-article-lookup-by-url-or-keyword/runs`, poll `GET /v2/actor-runs/{runId}` until `SUCCEEDED`, and read `GET /v2/datasets/{defaultDatasetId}/items`.
## Output
Each item is one record. Published fields include: `title`, `url`, `canonicalUrl`, `displayTitle`, `summary`, `description`, `language`, `pageId`, `wikidataId`, `wordCount`, `categories`, `thumbnail`, `originalImage`, `images`, `coordinates`, `languageCount`, `availableLanguages`, `lastModified`, `revisionId`, `lastEditor`.
Summarise what was found, cite the record URLs when present, and say how many items came back. Do not invent values for empty fields.
- Claude Code: save it as
~/.claude/skills/wikipedia-article-lookup-by-url-or-keyword/SKILL.md, or.claude/skills/wikipedia-article-lookup-by-url-or-keyword/SKILL.mdin a project. - Codex and other agents:
~/.agents/skills/wikipedia-article-lookup-by-url-or-keyword/SKILL.md, or.agents/skills/wikipedia-article-lookup-by-url-or-keyword/in a project. - Or let the skills CLI place it for your agent:
npx skills add https://recipeforagents.com --skill wikipedia-article-lookup-by-url-or-keyword - Set
APIFY_TOKENin the agent's environment.
Troubleshooting
Why does the client say Unauthorized or invalid token?
Every Apify Actor tool needs a signed-in Apify account. Reconnect the server so the OAuth sign-in runs again, or switch to the token variant: an Authorization: Bearer header with an API token from Apify Console, Settings, API and integrations. For a local server the token must be in the server's own env block, not only in your shell.
Source: Apify MCP server README
Why did my agent's tool list change after an update?
Without a tools parameter Apify's server loads its default tool set, which changes between releases. The URLs on this site pin the tools with ?tools=, so the agent always gets the same Actor tool plus fetch-actor-details. Apify's README gives the same advice for production.
Source: Apify MCP server README
What happens when the agent sends input the Actor rejects?
The server answers with the Actor's input schema, so the agent can fix the arguments and call again. The fetch-actor-details tool in every scoped URL lets it read that schema before the first call.
Source: Apify MCP server README
Questions
How do I connect Wikipedia Article Lookup by URL or Keyword to Claude?
In Claude Code run: claude mcp add --transport http wikipedia-article-lookup-by-url-or-keyword "https://mcp.apify.com/?tools=fetch-actor-details,vexaloom-labs/wikipedia-article-lookup-by-url-or-keyword". In Claude Desktop or claude.ai add a custom connector with the URL https://mcp.apify.com/?tools=fetch-actor-details,vexaloom-labs/wikipedia-article-lookup-by-url-or-keyword and sign in to Apify. The agent then gets one tool for this Actor plus a tool that reads its input schema.
What input does Wikipedia Article Lookup by URL or Keyword need?
No field is required by the published input schema. The example on this page uses the Actor's own Store prefill, so it is a sensible first run.
What does Wikipedia Article Lookup by URL or Keyword cost to run?
The Apify Store lists $0.99 per 1,000 results (pay per event) for this Actor, checked 2026-11-12. Runs are billed to the Apify account whose token or sign-in the agent uses; Apify platform usage can add to that.
Can I call Wikipedia Article Lookup by URL or Keyword as a plain HTTP API?
Yes. Server mode is on for this Actor, so a GET or POST to https://vexaloom-labs--wikipedia-article-lookup-by-url-or-keyword.apify.actor/ with an Authorization: Bearer header and the input as query parameters or a JSON body returns the results in the response. Each request runs in your own Apify account at the Actor's price.
Which tools does the MCP config give my agent?
2 tools: fetch-actor-details, vexaloom-labs--wikipedia-article-lookup-by-url-or-keyword. Apify's MCP server listed them for this exact URL on 2026-11-11.
More Wikipedia Actors
Bing Organic Search Results Scraper
Run keyword queries against Bing and get ranked organic results with title, URL, display URL and snippet for…
31 fields$0.99 per 1,000 resultsAhrefs Domain Rating, Backlinks & Traffic Lookup
Look up a domain's public Ahrefs Domain Rating, linking-website count, global rank, and estimated organic…
6 fields$0.99 per 1,000 resultsApartment Therapy Article Scraper
Scrape articles from Apartment Therapy - home decor, interior design, DIY, and small-space content from…
14 fields$0.99 per 1,000 resultsBaidu Web, Image & News Results Extractor
Runs search queries against Baidu's web, image, or news results and returns titles, URLs, snippets, dates…
9 fields$0.99 per 1,000 resultsComplete Page Capture - Screenshot & PDF
Capture complete full-page screenshots or PDFs of any URL list. Scrolls lazy content, waits for images and…
12 fields$0.99 per 1,000 resultsDecrypt Crypto News Finder by Category & Keyword
Search Decrypt's crypto, Web3, and AI news by keyword or category, or look up specific articles, for full…
7 fields$0.99 per 1,000 results