getlulu-dev I API

The I API from getlulu-dev — 1 operation(s) for i.

Operations 1

GET /i/{token} Impression #

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/getlulu-dev:getlulu-dev-i-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

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

getlulu-dev-i-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Lulu Ads I API
  version: 0.1.0
tags:
- name: I
paths:
  /i/{token}:
    get:
      summary: Impression
      description: 'Rendered-impression beacon. /slot returning an ad only proves output;

        this pixel firing proves a client actually displayed the sponsored unit

        — the ONLY event CPM billing/payout may count. Reuses the click token

        (same claims, same expiry). Short-TTL in-process dedupe swallows

        re-render bursts; CPM caps bound any residual overcount.


        `src=cli_server` is a distinct, weaker signal: the SDK itself (not a

        rendering client) fires this hit server-side the moment it appends a

        sponsored card to a CLI tool result, since terminal/CLI clients have no

        rendering engine to auto-fetch a pixel. It proves delivery (the card

        left our server in the tool response), never that a human saw it —

        logged as "cli_card_delivered", NOT "impression_rendered", and must

        never be counted toward CPM billing/payout.'
      operationId: impression_i__token__get
      parameters:
      - name: token
        in: path
        required: true
        schema:
          type: string
          title: Token
      - name: src
        in: query
        required: false
        schema:
          type: string
          default: ''
          title: Src
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
        '422':
          description: Validation Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HTTPValidationError'
      tags:
      - I
components:
  schemas:
    HTTPValidationError:
      properties:
        detail:
          items:
            $ref: '#/components/schemas/ValidationError'
          type: array
          title: Detail
      type: object
      title: HTTPValidationError
    ValidationError:
      properties:
        loc:
          items:
            anyOf:
            - type: string
            - type: integer
          type: array
          title: Location
        msg:
          type: string
          title: Message
        type:
          type: string
          title: Error Type
        input:
          title: Input
        ctx:
          type: object
          title: Context
      type: object
      required:
      - loc
      - msg
      - type
      title: ValidationError