iLang Agent API

The Agent API from iLang — 3 operation(s) for agent.

Operations 3

GET /api/agent/lookup Look up an iLang verb, modifier, entity or declaration #
GET /api/agent/faq Find the published FAQ entry closest to a question #
GET /api/agent/health Health #

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • 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.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/ilang-ai:ilang-ai-agent-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

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 Specification

ilang-ai-agent-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: iLang public lookup Agent API
  version: 1.0.0
  description: 'Read-only lookup over the published iLang dictionary and FAQ. No authentication.

    Source data: ilang-ai/ilang-dict train.csv and the FAQ on ilang.ai.'
servers:
- url: https://ilang.ai
tags:
- name: Agent
paths:
  /api/agent/lookup:
    get:
      operationId: lookup
      summary: Look up an iLang verb, modifier, entity or declaration
      parameters:
      - name: q
        in: query
        required: true
        schema:
          type: string
        description: Term, alias or keyword, for example XLAT, lng, @PREV, BUDGET, translate
      responses:
        '200':
          description: Matches (possibly empty; not_found=true when empty)
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/LookupResult'
        '400':
          description: Missing or empty q
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
      tags:
      - Agent
  /api/agent/faq:
    get:
      operationId: faq
      summary: Find the published FAQ entry closest to a question
      parameters:
      - name: q
        in: query
        required: true
        schema:
          type: string
      responses:
        '200':
          description: Best matching FAQ entries with source_url; not_found=true when nothing matches
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/FaqResult'
        '400':
          description: Missing or empty q
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
      tags:
      - Agent
  /api/agent/health:
    get:
      operationId: health
      summary: Health
      responses:
        '200':
          description: ok
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Health'
      tags:
      - Agent
components:
  schemas:
    Entry:
      type: object
      properties:
        type:
          type: string
        name:
          type: string
        alias:
          type: string
        category:
          type: string
        meaning:
          type: string
        values:
          type: string
        source_url:
          type: string
      required:
      - type
      - name
    FaqResult:
      type: object
      properties:
        query:
          type: string
        not_found:
          type: boolean
        matches:
          type: array
          items:
            type: object
            properties:
              question:
                type: string
              answer:
                type: string
              source_url:
                type: string
      required:
      - query
      - not_found
      - matches
    Health:
      type: object
      required:
      - status
      properties:
        status:
          type: string
          enum:
          - ok
        service:
          type: string
        time:
          type: string
          format: date-time
    LookupResult:
      type: object
      properties:
        query:
          type: string
        not_found:
          type: boolean
        matches:
          type: array
          items:
            $ref: '#/components/schemas/Entry'
        dictionary_version:
          type: string
        source:
          type: string
      required:
      - query
      - not_found
      - matches
    Error:
      type: object
      required:
      - error
      properties:
        error:
          type: string
          description: Machine-readable reason, currently always "missing q"
        example:
          type: string
          description: A request path that succeeds