Iridium Iridium LinkedIn For AI Agents API

The Iridium LinkedIn For AI Agents API from Iridium — 1 operation(s) for iridium linkedin for ai agents.

GitHub OpenAPI

Operations 1

GET / Root #

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/iridiumhqmcp-com:iridiumhqmcp-com-iridium-linkedin-for-ai-agents-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

iridiumhqmcp-com-iridium-linkedin-for-ai-agents-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Iridiumhqmcp Com Iridium LinkedIn For AI Agents API
  version: 0.1.0
  description: 'Operations tagged Iridium LinkedIn For AI Agents across 2 of this provider''s published API definitions: openapi.json, iridiumhqmcp-com-openapi.json. Each path carries the servers of the definition it was published in.'
tags:
- name: Iridium LinkedIn For AI Agents
paths:
  /:
    get:
      summary: Root
      description: 'Entry point for an agent that has the hostname and nothing else.


        GET / was a 404, which is a dead end: the discovery documents all exist but you had to

        already know their paths to find them. Every URL below is a document that was already

        being served, so this adds a way in and no new surface. Unauthenticated by design, and

        it reveals nothing that /.well-known does not.


        The API catalogue and auth.md live on the public site, not here, because that is the

        origin that publishes the agent-facing set. One copy, linked from both.'
      operationId: root__get
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
      tags:
      - Iridium LinkedIn For AI Agents
components:
  securitySchemes:
    HTTPBearer:
      type: http
      scheme: bearer
x-refined-from:
- openapi.json
- iridiumhqmcp-com-openapi.json
x-provenance:
  method: harvested
  publisher: Iridium
  source: https://api.iridiumhqmcp.com/openapi.json
  note: split by refine-openapis from the provider's own published document, verified by fetch (openapi/_original/*.fetch.json);
    stamped by stamp-openapi-provenance.py (roadmap#793)