canonical: https://jentic.com/apis/worldcoinindex.com/worldcoinindex

# WorldCoinIndex API

WorldCoinIndex cryptocurrency market data API providing ticker information, market prices, and volume data for various cryptocurrency pairs across multiple fiat currencies. The API exposes 4 endpoints secured with apiKey authentication.

## For AI agents

Programmatically get ticker data, get all markets (v2). Covers 4 operations with apiKey authentication.

## Scope

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

## Capabilities

- Get ticker data
- Manage developer tools data programmatically
- Integrate WorldCoinIndex API into automated workflows
- Query and filter WorldCoinIndex API records by parameters
- Monitor WorldCoinIndex API operational status and events

## Use cases

### Developer Tools Operations

Use the WorldCoinIndex API to perform developer tools operations programmatically. The API provides 4 endpoints covering core functionality including get ticker data, get all markets (v2), get all markets (deprecated).

Example prompt: Call GET /ticker to get ticker data

### Automated Market Data Management

Automate market data operations by combining multiple WorldCoinIndex API endpoints. Agents can get all markets (v2) and then get all markets (deprecated) in a single workflow.

Example prompt: Call GET /v2getmarkets to get all markets (v2), then verify the result

### AI Agent Integration via Jentic

AI agents discover and call WorldCoinIndex 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 'get ticker data', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/ticker` | Get ticker data |
| GET | `/v2getmarkets` | Get all markets (v2) |
| GET | `/getmarkets` | Get all markets (deprecated) |
| GET | `/json` | Get all data (deprecated) |

## Key resources

- **Market Data** — Operations related to Market Data

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 49 / 100
- **Maturity:** Foundational
- **Dimensions:**
  - Foundational Compliance: 100 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 50 / 100
  - Agent Usability: 94 / 100
  - Security: 15 / 100
  - AI Discoverability: 100 / 100
- **View full report:** https://jentic.com/apis/worldcoinindex.com/worldcoinindex/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring the WorldCoinIndex API by hand means passing its API key on every query and handling responses across its ticker and markets endpoints yourself. Through Jentic you install once, import the WorldCoinIndex API from the API Directory, store the API key once, and your agent calls it.
- **Permission scoping:** The WorldCoinIndex API is read-only market data with no resource id in the URL path, so scope by operation: limit the agent to the operations it needs, such as reading ticker data or listing markets. You choose that set, so nothing beyond those reads is available unless you add it.
- **Credential handling:** Your WorldCoinIndex API key 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 'get ticker data' or 'list markets', and Jentic returns the matching WorldCoinIndex API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

### What authentication does the WorldCoinIndex API use?

The WorldCoinIndex API uses an API key passed in the `key` query. 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 get ticker data with the WorldCoinIndex API?

Yes. Use the GET /ticker endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the WorldCoinIndex 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 get ticker data through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'get ticker data'. Jentic returns the matching WorldCoinIndex API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the WorldCoinIndex API have?

The WorldCoinIndex API exposes 4 endpoints covering market data operations.

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

Yes. The WorldCoinIndex API is read-only market data, so with Jentic One, which you host yourself, you scope the agent by operation and grant only the calls it needs. You might allow reading ticker data with GET /ticker and listing markets with GET /v2getmarkets while withholding the deprecated market and data endpoints. Because your own rules decide which operations and credentials are available, nothing beyond the reads you approve is exposed.