Install Jentic One Beta

Connect the Flickr API Schema to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Flickr API Schema, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fflickr.com%2Fflickr" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fflickr.com%2Fflickr" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Flickr API Schema API.

Search the public Flickr photo corpus by tags, text, license, or user with flickr.photos.search

Read photo metadata, sizes, EXIF data, and license details for any accessible photo

Browse photoset, gallery, and group-pool contexts for a given photo

List the photos a person has uploaded or favorited and read their public profile

GET STARTED

Start building with Flickr API Schema API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Flickr API Schema API for, with concrete tasks.

★ License-aware image discovery

Editorial teams and AI agents searching for reusable imagery filter Flickr by license through flickr.photos.search and flickr.photos.licenses.getInfo. Combined with flickr.photos.getSizes, this returns a vetted list of Creative Commons photos at the resolution the publication needs, with attribution data already attached.

Search for Creative Commons photos tagged 'mountains', then return the photo IDs, sizes, and license names for the top 10 results

Photo metadata enrichment

Photo-management tools enrich an image record with EXIF camera and lens data, GPS context, and license metadata pulled from Flickr. The flickr.photos.getInfo, flickr.photos.getExif, and flickr.photos.getSizes calls together expose enough detail to populate a digital-asset-management record from a single photo URL.

Given a Flickr photo ID, fetch its EXIF, sizes, and license, and write a JSON record with camera model, focal length, dimensions, and licence name

Community photo curation

Group administrators and curators read pool members, group info, and discussion topics through flickr.groups.getInfo, flickr.groups.pools.getPhotos, and the flickr.groups.discuss endpoints. This drives moderation tooling and lets curators feature member photos in galleries with citation context.

List the most recent 50 photos in a Flickr group pool and the latest 5 discussion topics in that group

AI agent image research

An AI research agent uses Flickr through Jentic to find Creative Commons reference photos for a writing or design task, retrieve their full sizes and licence names, and cite them correctly. Jentic returns the right Flickr operation for each step of the workflow without the agent browsing all 25 endpoints by hand.

Find five Creative Commons photos of red pandas, return the original-size URL and required attribution string for each

Key Endpoints

25 endpoints — the flickr api exposes a swagger-described subset of flickr's photo-sharing platform, covering photo and photoset metadata, search, exif and license data, group pools, galleries, favorites, and user profiles.

METHOD

PATH

DESCRIPTION

GET

/rest?method=flickr.photos.search

Search the public photo corpus

GET

/rest?method=flickr.photos.getInfo

Get full metadata for a photo

GET

/rest?method=flickr.photos.getExif

Read EXIF data for a photo

GET

/rest?method=flickr.photos.getSizes

List the available sizes and download URLs for a photo

GET

/rest?method=flickr.photos.licenses.getInfo

Look up Creative Commons and other license names

GET

/rest?method=flickr.people.getPhotos

List photos uploaded by a specific user

POST

/upload

Upload a new photo on behalf of an authenticated user

GET

/rest?method=flickr.photos.search

Search the public photo corpus

GET

/rest?method=flickr.photos.getInfo

Get full metadata for a photo

GET

/rest?method=flickr.photos.getExif

Read EXIF data for a photo

GET

/rest?method=flickr.photos.getSizes

List the available sizes and download URLs for a photo

GET

/rest?method=flickr.photos.licenses.getInfo

Look up Creative Commons and other license names

GET

/rest?method=flickr.people.getPhotos

List photos uploaded by a specific user

POST

/upload

Upload a new photo on behalf of an authenticated user

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the Flickr API by hand means signing every request with OAuth 1.0a using consumer keys, secrets, and per-user tokens, and learning its REST-over-query method conventions with your own retries. Through Jentic you install once, import Flickr from the API Directory, store the credentials once, and your agent calls it.

Permission scoping

Flickr selects its target through the method query parameter rather than an owned resource in the URL path, so limit the agent to the operations it needs, such as photo search and metadata retrieval, and leave authenticated upload out of the allowed set unless required. You choose which operations it may call.

Credential isolation

Your Flickr OAuth 1.0a keys, secrets, and per-user tokens are stored once, encrypted, by your own Jentic One instance and used to sign requests at execution time. They never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'find Creative Commons photos of mountains', and Jentic returns the matching flickr.photos.search call with its input schema so the agent calls the right method without learning Flickr's REST-over-query conventions.

FAQs

Specific to using Flickr API Schema API through Jentic.

What authentication does the Flickr API use?

The Flickr API uses OAuth 1.0a request and access tokens at /oauth/request_token and /oauth/access_token. Through Jentic the OAuth secrets are stored in the encrypted vault and request signing happens at execution time, so an agent never holds the raw consumer secret.

Can I filter Flickr photos by license with the API?

Yes. flickr.photos.search accepts a license parameter, and flickr.photos.licenses.getInfo returns the name and URL for each license code so the integration can render correct attribution.

How do I read EXIF data for a Flickr photo?

Call flickr.photos.getExif with the photo ID. The response returns camera model, lens, focal length, ISO, aperture, and other tags exposed by the photographer.

What are the rate limits for the Flickr API?

Flickr publishes a default cap of 3,600 calls per hour per API key, with bursts subject to throttling. Treat 429 and 503 responses as the source of truth and back off accordingly.

How do I search Flickr photos through Jentic?

Search Jentic for 'search Flickr photos', load the schema for flickr.photos.search, and execute the call with your tags or text query. Install with pip install jentic and run it through Jentic One, the self-hosted execution layer.

Can I upload a photo to Flickr through this API?

Yes. POST a multipart upload to /upload with an OAuth-signed Authorization header. The user must have authorized your application with write scope first.

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

Yes. Because the Flickr API picks its target through the method query parameter rather than a resource in the URL path, your self-hosted Jentic One instance lets you decide which methods the agent may call. You can allow read operations such as flickr.photos.search, flickr.photos.getInfo, and flickr.photos.getExif while leaving the authenticated /upload endpoint out of the permitted set. Your own rules govern which operations and which OAuth credentials the agent uses, so it can only run the Flickr calls you have approved.

Flickr API Schema

Name: Flickr API Schema API
Brand: Flickr API
Availability: InStock

Official vendor OpenAPI document · agent-readyMediaImage Processingoauth125 EndpointsREST

For Agents

Search Flickr photos, read photo metadata and EXIF, browse groups, galleries, and favorites, and upload images on behalf of an authenticated user.

Use for: Search Flickr for Creative Commons photos of the Eiffel Tower, Get the EXIF data for a specific Flickr photo, List all photos a Flickr user has uploaded, Find which group pools contain a given photo

Not supported: Does not handle image editing, video hosting, or payment processing - use for Flickr photo search, metadata retrieval, and authenticated photo upload only.

The Flickr API exposes a Swagger-described subset of Flickr's photo-sharing platform, covering photo and photoset metadata, search, EXIF and license data, group pools, galleries, favorites, and user profiles. It also includes the OAuth request and access token endpoints plus the photo upload endpoint, so an integration can authenticate a user, search the public photo corpus, and read context such as comments, sizes, and discussion threads.

Jentic One on Github View OpenAPI Document