canonical: https://jentic.com/apis/wikimedia.org/wikimedia

# Wikimedia REST API

This API provides cacheable and straightforward access to Wikimedia content and data, in machine-readable formats. Global Rules - Limit your clients to no more than 200 requests/s to this API. Each API endpoint's documentation may detail more specific usage limits. - Set a unique `User-Agent` or `Api-User-Agent` header that allows us to contact you quickly. Email addresses or URLs of contact pages. The API exposes 3 endpoints secured with apiKey authentication.

## For AI agents

Programmatically check and normalize a tex formula., get a previously-stored formula. Covers 3 operations with apiKey authentication.

## Scope

Does not handle payments, communications, or developer tools - use for crm only.

## Capabilities

- Check and normalize a TeX formula.
- Get a previously-stored formula
- Integrate Wikimedia REST API into automated workflows
- Query and filter Wikimedia REST API records by parameters
- Monitor Wikimedia REST API operational status and events

## Use cases

### CRM Operations

Use the Wikimedia REST API to perform crm operations programmatically. The API provides 3 endpoints covering core functionality including check and normalize a tex formula., get a previously-stored formula, get rendered formula in the given format..

Example prompt: Call POST /media/math/check/{type} to check and normalize a tex formula.

### Automated Math Management

Automate math operations by combining multiple Wikimedia REST API endpoints. Agents can get a previously-stored formula and then get rendered formula in the given format. in a single workflow.

Example prompt: Call GET /media/math/formula/{hash} to get a previously-stored formula, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Wikimedia REST API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually.

Example prompt: Search Jentic for 'check and normalize a tex formula.', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | /media/math/check/{type} | Check and normalize a TeX formula. |
| GET | /media/math/formula/{hash} | Get a previously-stored formula |
| GET | /media/math/render/{format}/{hash} | Get rendered formula in the given format. |

## Key resources

- **Math** — formula rendering

## Why Jentic

- **Setup:** Wiring the Wikimedia REST API by hand means handling its permission cookie header, targeting wikimedia.org/api/rest_v1, and passing type, hash, and format parameters yourself. Through Jentic you install once, import the Wikimedia REST API from the API Directory, store the credential once, and your agent calls it.
- **Permission scoping:** Wikimedia puts the format and hash in the URL path (/media/math/render/{format}/{hash}), so a rule can pin your agent to rendering or fetching a given formula. You choose the operations it may call, so anything beyond the math check, formula, and render set is not included unless you add it.
- **Credential handling:** Your Wikimedia credential is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'check a TeX formula' or 'render a math formula', and Jentic returns the matching Wikimedia operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Hubspot** — Alternative crm API
- **Salesforce** — Alternative crm API
- **Pipedrive** — Complementary crm API
- **Zoho** — Complementary crm API

## FAQ

### What authentication does the Wikimedia REST API use?

The Wikimedia REST API uses an API key passed in the `cookie` header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I check and normalize a tex formula. with the Wikimedia REST API?

Yes. Use the POST /media/math/check/{type} endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Wikimedia REST API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I check and normalize a tex formula. through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'check and normalize a tex formula.'. Jentic returns the matching Wikimedia REST API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Wikimedia REST API have?

The Wikimedia REST API exposes 3 endpoints covering math operations.

### Can I limit what my agent is allowed to do with the Wikimedia REST API?

Yes. Because you run Jentic One yourself, your own rules decide which of the Wikimedia REST API operations your agent may call, so you can grant only the math check (POST /media/math/check/{type}), formula fetch (GET /media/math/formula/{hash}), and render (GET /media/math/render/{format}/{hash}) operations you actually need. Since the format and hash are carried in the URL path, a rule can pin your agent to rendering or fetching a specific formula rather than the full set. Anything outside the operations you approve is not available to the agent unless you add it, and the credential is injected at execution time so it never enters the agent's context.