Skip to main content
Glama

livepair-hub

by com.livepairai
OverviewDiscussionsAdmin

Generate an image or video (paid, x402)

generate_image

Render an image or video with a catalog model (t2i, i2i, t2v, i2v) — including the private model line flagged private=true in list_models. This is a PAID call, two rails: (1) x402 — the endpoint answers HTTP 402 with payment requirements (USDC on Base mainnet — priced per call, video billed per second per model rate); retry with a PAYMENT-SIGNATURE header settling one requirement (use an x402-capable client like @x402/fetch). (2) API key — sign up at https://livepairai.com/auth/sign-up, create a key at /dashboard/settings, send x-api-key: lp_…; the call bills your prepaid credit balance and skips the 402 entirely. On success returns {status:'done',url}; slow jobs return a jobId to poll for free.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
imageNoSource image for i2i/i2v models — public http(s) URL or data:image URI. Use AI-generated or owned images only — never real-person photos without consent
payerNoYour 0x… wallet — applies your volume-tier discount; must equal the wallet signing the payment
promptYesThe prompt to render — call enhance_prompt first for best results
modelIdNoModel id from list_models (default: fastest t2i)
durationNoVideo length in seconds (video models)
resolutionNoVideo resolution tier (video models)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / payer
      Added value: +{
+  "description": "Your 0x… wallet — applies your volume-tier discount; must equal the wallet signing the payment",
+  "type": "string"
+}
  2. Changed1 schema field changed
    • changedInput schema / properties / image / description
      Previous value: -"Source image for i2i/i2v models — public http(s) URL or data:image URI"New value: +"Source image for i2i/i2v models — public http(s) URL or data:image URI. Use AI-generated or owned images only — never real-person photos without consent"
  3. Changed3 schema fields changed
    • addedInput schema / properties / duration
      Added value: +{
+  "description": "Video length in seconds (video models)",
+  "type": "number"
+}
    • addedInput schema / properties / image
      Added value: +{
+  "description": "Source image for i2i/i2v models — public http(s) URL or data:image URI",
+  "type": "string"
+}
    • addedInput schema / properties / resolution
      Added value: +{
+  "description": "Video resolution tier (video models)",
+  "type": "string"
+}
  4. Added

TDQS

A4.4/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Goes well past the annotations: it discloses that this is a paid mutation, the exact 402 handshake and PAYMENT-SIGNATURE retry, USDC/Base mainnet pricing, per-second video billing, API-key billing against prepaid credit, and the success shape plus jobId polling for slow jobs. Annotations only say it is a non-read-only open-world call; the description supplies the operational reality.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three dense sentences, front-loaded with the render purpose before payment mechanics. Every clause carries information, though the single-sentence payment block is long enough to be slightly heavy to parse.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a six-parameter paid generation tool with no output schema, the description covers the payment prerequisites, the return contract ({status:'done',url}), and the async jobId path. Nothing needed to invoke it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3 — modelId, image, prompt, duration, resolution and payer are all documented in the schema itself. The description reinforces a couple of them (model ids come from list_models, video billed per second) but adds no format or syntax detail beyond what the schema already states.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Opens with a specific verb and dual resource ('Render an image or video') and enumerates the four supported modes (t2i, i2i, t2v, i2v), which no sibling tool covers. It also references list_models for model discovery, letting an agent separate this from chat_text or enhance_prompt without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It clearly states the two payment conditions under which the call succeeds (x402 402/settlement vs x-api-key with prepaid credit) and notes the private model line is included. It does not explicitly name which sibling to use instead when only text is wanted, but the context for invoking it is unambiguous.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All livepair-hub toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources