Does the CompressGIF API work synchronously or asynchronously?

It is asynchronous. You create a compression job from a source URL and then poll the job for its status and a temporary download link once processing completes. This means an agent submits the work and checks back rather than holding a request open for the whole compression.

What are the rate limits for the CompressGIF API?

The OpenAPI spec meters work by a shared credit balance rather than a fixed request-per-second limit: valid output consumes credits even when the target is not met, while failed processing, polling, and downloads consume none. Check https://compressgif.net for the credit and throughput limits on your plan.

Is there a CompressGIF MCP server?

Yes, CompressGIF offers an MCP server that shares its credit balance with this REST surface. You can also connect the CompressGIF API directly through Jentic: your agent gets the full 3-endpoint surface without loading another server's tool definitions into its context, your credential is injected at call time by your self-hosted instance instead of living in an MCP config, and your rules decide which operations the agent may call.

Can I limit what my agent is allowed to do with the CompressGIF API?

Yes. Because the job id travels in the URL path, you write a rule that allows only the create-compression and read-status operations and leaves the usage read out, or the reverse. The agent can then compress GIFs and fetch their download links but touch nothing else, and every call it makes is logged.

How do I compress a GIF through Jentic?

Import the CompressGIF API from the Jentic API Directory, store your API key once, and have your agent search Jentic for 'compress a GIF'. Jentic returns the create-compression operation with its input schema so the agent sends the `sourceUrl` and an idempotency key and then polls for the download link. To run it on your own infrastructure, install Jentic One from its GitHub repo.