The practical Tool API

One API for the work around your AI.

Give your product, script, or agent reliable tools for images, PDFs, websites, audio, video, and recurring work—without integrating a different service for every task.

Free to start REST + MCP One key Jobs + webhooks

Start with one request

Useful before the SDK finishes installing.

Call a tool directly with curl. Add your key when you need authenticated limits, saved jobs, and paid operations.

See JavaScript and Python examples →
# No-auth connectivity check
curl https://agentmediatools.com/api/uuid

{
  "uuid": "550e8400-e29b-41d4-a716-446655440000"
}

# The same key unlocks every authenticated tool
curl -X POST https://agentmediatools.com/api/resize-image \
  -H "Authorization: Bearer $AMT_API_KEY" \
  -F "image=@product.jpg" -F "width=1200"

One integration, practical coverage

Tools your application actually needs.

Start with a single operation. Keep the same authentication, limits, job handling, and billing as your workflow grows.

🖼️

Images

Resize, convert, compress, crop, remove backgrounds, inspect, and generate.

resize_image · compress_image · generate_image
📄

PDFs & documents

Merge, split, extract, OCR, fill forms, convert, and prepare documents.

merge_pdf · pdf_to_markdown · ocr
🌐

Web intelligence

Read public pages, capture screenshots, extract structured data, and monitor changes.

browse_web · screenshot · structured_scrape
🎧

Audio & video

Transcribe, trim, convert, inspect metadata, and run generation workflows.

transcribe_audio · trim_video · video_info
⚙️

Jobs & automation

Move longer work off the request path, poll status, schedule runs, or receive webhooks.

jobs · schedules · signed_webhooks
{ }

Developer utilities

Use focused helpers for JSON, hashes, UUIDs, timestamps, QR codes, and more.

uuid · hash · json_tools · qr

Use it your way

One catalog. Three ways in.

The Tool API is the shared product surface—not a separate collection of endpoints for every client.

MCP

Expose the same supported tools directly to Claude, Cursor, and compatible agent hosts.

Connect with MCP →
Browser workspace

Try the operation by hand, confirm the output, then automate it when you are ready.

Open the workspace →

Built for more than a demo

Fewer integrations. Better control.

The hard part is rarely the first API call. It is keeping credentials, asynchronous work, spending, retries, and results understandable after an experiment becomes a product.

One API key across the tool catalog
Explicit free limits and credit costs
Asynchronous jobs with retained IDs and status
Signed webhooks for durable completion delivery
Spend policy, approvals, receipts, and key controls
POST /api/resize-imagemedia
POST /api/pdf-to-markdowndocuments
POST /api/browser/tasksweb
POST /api/jobsasync work
POST /api/user-webhooksdelivery

Tool API questions

Simple answers before your first call.

What is a Tool API?

A Tool API lets software and AI agents call focused capabilities such as image resizing, PDF processing, website reading, transcription, and scheduled jobs. Here, they share one REST API and supported MCP tools.

Can I try the Tool API for free?

Yes. Some tools work without authentication, and a free account provides an API key for authenticated tools and higher shared daily usage.

Can AI agents use the same API tools?

Yes. Applications and scripts can use REST, while compatible AI agents can use supported tools through MCP. Both use the same account and catalog.

What kinds of API tools are included?

The catalog covers images, PDFs and documents, public web intelligence, audio and video, developer utilities, asynchronous jobs, schedules, and signed webhook delivery.

Your first request is free

Pick one tool. Keep one integration.

Create a key, test a real operation, and add more tools only when your product needs them.