What authentication does the Imgur API use?

Imgur supports two schemes: a client ID passed as Authorization: Client-ID for anonymous uploads, and OAuth 2.0 for user-authenticated actions like favouriting or managing the user's account. Through Jentic both flows are vaulted - the client ID and the OAuth token never enter the agent context.

Can I upload an image anonymously?

Yes. POST /image with the Authorization: Client-ID header. The response returns the public link plus a deletehash that can later be used to remove the image without OAuth.

How do I add an image to an existing album?

POST /album/{albumHash}/add with the image hashes that should be added. Use POST /album/{albumHash}/remove_images to take them out again. Both calls require OAuth when the album belongs to a signed-in user.

How do I upload an image through Jentic?

Run pip install jentic, search for 'upload an image to Imgur', load the /image POST schema, and execute with the image bytes. Jentic supplies the client ID or OAuth token from the vault depending on which is configured.

What are the rate limits for the Imgur API?

Imgur enforces per-IP and per-application credit limits documented on their developer site. The OpenAPI spec does not encode these limits directly; back off on HTTP 429 responses and check the X-RateLimit headers on each response.

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

Yes. Because you run Jentic One yourself, your own rules decide which Imgur operations the agent may call, so you can grant uploads and reads while leaving out destructive ones like deleting an image or removing images from an album. Imgur puts the image and album hash directly in the URL path, such as /image/{imageHash} and /album/{albumHash}/add, so a rule can pin the agent to a single image or album. Your Imgur client ID and OAuth token are held by your own instance and injected only for the operations you have allowed.