tagrly.com valid
Tagrly
Tagrly turns a business's own photo library into an API an AI agent can call. A customer connects a Google Drive or Dropbox folder; Claude vision reads every image into 34 structured fields; an agent then POSTs a plain-English page topic to `/api/page` and gets back a page-ready set of that business's own photographs with alt text already rewritten for the topic, plus an honest gap signal naming the shots the library does not contain. One endpoint, `POST /api/try/analyze-photo`, takes no account
Their llms.txt
The beginning of the file, from our validated copy saved 2026-10-27T11:56:23.273Z. Cached copy · Source on tagrly.com
# Tagrly
> Tagrly turns a business's own photo library into an API an AI agent can call. A customer connects a Google Drive or Dropbox folder; Claude vision reads every image into 34 structured fields; an agent then POSTs a plain-English page topic to `/api/page` and gets back a page-ready set of that business's own photographs with alt text already rewritten for the topic, plus an honest gap signal naming the shots the library does not contain. One endpoint, `POST /api/try/analyze-photo`, takes no account at all. Tagrly is for putting a customer's own photographs into generated pages, posts, listings and decks. It is not a stock-photo service and it does not generate images.
Agent instructions. Start here: `POST https://tagrly.com/api/try/analyze-photo` with a single image as `multipart/form-data` under the field name `photo`. No key, no header, no signup. It runs the production analyzer on that one photo, returns the structured reading, and persists nothing. Five reads an hour per connection, 8MB per upload, JPEG/PNG/WebP/HEIC/HEIF/AVIF/GIF. That is the whole of what you can do without credentials, and it is enough to show a user what the product does.
Everything else is workspace-scoped and needs one header: `Authorization: Bearer tagrly_pk_<workspace-slug>_<32 hex chars>`. Keys are self-serve: a signed-in workspace owner or admin creates one at https://tagrly.com/settings#api-keys (Settings, API access), names it after the tool that will hold it, and sees the full key exactly once. There is no API endpoint that mints a key. If you are an agent and your user has no key, say so and ask them to create one there; do not guess at an issuance route. Once you have a key, `POST /api/page` with `{"topic": "..."}` is the call to make first, and every other endpoint is a refinement of it.
MCP: the same catalog is served over the Model Context Protocol at `https://tagrly.com/mcp` (Streamable HTTP, stateless). If your client speaks MCP, connect there with the key as an `Authorization: Bearer` header instead of hand-writing HTTP calls: six tools (search_photos, find_photos, get_page_images, get_image, log_usage, list_collections) that dispatch through the same API with identical scoping and metering. Setup recipes per client: https://tagrly.com/mcp-server
How to ingest this. Claude Code: WebFetch https://tagrly.com/llms-full.txt for the complete reference in one request, or `claude mcp add --transport http tagrly https://tagrly.com/mcp` for tools. Claude.ai, ChatGPT and Gemini: paste that URL into the conversation. Cursor and Windsurf: add it to your project rules or context. Anything else: a plain GET on https://tagrly.com/agent-guide returns readable HTML.
## Primary documentation for agents
- [Full reference, plain text](https://tagrly.com/llms-full.txt): every endpoint, request field, response field, applied default, limit and error code in one file. This is the fetch to make.
- [Agent guide](https://tagrly.com/agent-guide): the same reference
…
Related sites
Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.
| Domain | Title | Category | Country | Authority | llms.txt | llms-full.txt | Save |
|---|---|---|---|---|---|---|---|
| productai.photo | ProductAI | interface AI and machine learning APIs and SDKs | US | 52 | ✓ | ||
| playbook.com | Playbook | transactional Gaming Productivity +1 | — | 63 | ✓ | ✓ | |
| idimager.com | photosupreme | interface Developer tools Data and analytics | US | 50 | ✓ | ||
| x02.me | X02 | interface AI agents and MCP APIs and SDKs | — | 45 | ✓ | ✓ | |
| twoshot.app | TwoShot | interface AI and machine learning AI agents and MCP +1 | — | 48 | ✓ | ||
| gencatalog.app | GenCatalog | documentation Productivity AI and machine learning | — | 46 | ✓ | ✓ | |
| ximilar.com | Ximilar: Visual AI for Business: VISUAL AI FOR BUSINESS | interface AI and machine learning APIs and SDKs | — | 51 | ✓ | ||
| dokkio.com | Dokkio | interface Productivity AI and machine learning | US | 49 | ✓ |
Machine-readable: GET /v1/resolve?q=tagrly.com · GET /v1/domain/tagrly.com · this page as Accept: application/json or text/markdown · MCP lookup_domain
Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.
Own or manage this website?
If you own or manage tagrly.com, you can update its listing and review file health, discovery activity and score history.
Manage this listing — optional
What verification unlocks
See how your site is discovered—and control what agents see.
- See your website in the map
Review your indexed topics, nearby publishers sharing headings, measured listing exposure and map snapshots in a private report for your website.
- Control what agents see
Edit your listing description, tags, public contact details and additional llms.txt paths. Publish your terms for automated access, attribution and pricing.
- Make your profile eligible for search
A valid, listed, unblocked, verified profile can appear in our publisher sitemap and become eligible for search-engine visibility. Search engines decide what to index and rank.
- Appear in our llms-full.txt
Eligible verified publishers are listed by name, with their file links and summaries, in the service overview agents can read.
Free. No account registration, backlink or payment required. Public discovery remains available without verification.
Let your coding agent verify it
If your coding agent is authorized to manage this website, paste these instructions into it.
Claim my listing on Agent Web Map for tagrly.com:
1. POST https://agentwebmap.com/v1/sites/tagrly.com/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://tagrly.com/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/tagrly.com/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/tagrly.com).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verifyCorrections or removal requests: contact the directory.