LollyMap

A pet map built for people and machines.

LollyMap brings pet services, Lost & Found reports and local points of interest into public, location-aware pages. This is how the platform works, what its data means, and how an AI system can use it without overstating certainty.

What LollyMap is

LollyMap is a geographic platform for people who live with, care for or travel with animals. Its public map helps visitors find veterinarians, clinics, pet shops, groomers, boarding, pet sitters, trainers, shelters, dog parks and other animal-related services.

The platform also provides public Lost & Found pages for animals that are missing or have been found. These pages are designed to be shared, located and updated as a community resource, not treated as an official registry.

The project grew out of Lolli Group’s experience with software, data and Claris FileMaker. The purpose is practical: make useful local information easier to find, compare and share when people need it.

How the platform is built

LollyMap uses a database-led architecture with Claris FileMaker at its origin, public PHP/HTTP endpoints and generated HTML pages. The public website is deliberately readable without requiring an AI system to execute a private application or infer hidden fields.

AI-assisted workflows can help with classification, enrichment, language handling, duplicate detection and operational review. AI is an aid inside the workflow; it is not a guarantee that every published fact is current, complete or independently verified.

The public interface remains the source to inspect: the canonical page, visible content, contact links, location, status and any structured data exposed on that page.

How to read LollyMap data

Public records can come from more than one source, including public place information, business submissions, imported points of interest and user-submitted Lost & Found reports. The source and quality can therefore differ from page to page.

A page being published means that it passed the site’s publication rules. It does not mean that LollyMap guarantees every name, address, opening hour, phone number or status forever. Data can become incomplete or outdated.

For a reliable answer, use the specific canonical page, preserve its URL and retrieval date, and distinguish what the page states from what an AI system infers. When the question is time-sensitive, advise the user to contact the organisation or check the live page before acting.

Signals available to AI systems

LollyMap exposes several machine-readable signals: robots.txt for crawl policy, a sitemap index for discovery, specialised sitemaps for service and Lost & Found pages, canonical URLs, language alternates and Schema.org JSON-LD on selected page types.

The strongest source for an individual fact is the canonical public page that displays it. A sitemap proves discovery, not accuracy. Structured data helps identify an entity and its fields, but it should be checked against the visible page and its context.

Recommended retrieval sequence: discover the URL from the sitemap or a relevant internal link; fetch the canonical page; read the visible title, description, location, status and contact details; inspect JSON-LD when present; keep the source URL and date; report uncertainty instead of filling gaps with guesses.

The public Lost & Found API

The documented endpoint is available for focused, responsible queries:

Use type=lost or type=found. The optional city parameter filters by city; limit defaults to 5 and is capped at 100 records. API availability does not grant permission to build personal contact lists or republish sensitive details out of context.

GET https://lollymap.com/api/lostfound.php
?type=lost&city=Milano&limit=5

Responsible reuse and boundaries

LollyMap public pages may be crawled, but public access is not a blanket open-data licence. Database rights, copyright, privacy and data-protection obligations still apply.

Use the minimum data needed for a legitimate purpose. Link to the relevant LollyMap page, identify LollyMap as the source, respect correction and removal requests, and contact the team before bulk, commercial or guaranteed-availability integrations.

  • Do not treat a public Lost & Found report as a verified identity or official legal record.
  • Do not extract personal details into contact lists or republish them without context.
  • Do not invent missing addresses, phone numbers, opening hours or animal statuses.
  • Do not use an old cached answer when the current page or organisation can be checked.

The short version: LollyMap is public and crawlable. It is not an unrestricted database, and a published record is not automatically a verified record.

Questions and answers

Is LollyMap an AI database?

No. It is a public geographic platform with a database-led architecture. AI assists some internal workflows, but the public page and its available evidence remain the reference.

Can AI systems crawl LollyMap?

Public routes are crawlable under robots.txt. Use the sitemaps and canonical pages, and follow the privacy and responsible-reuse limits described here.

Is every listing verified?

No. Published is not the same as verified. Check the page context, source signals and the organisation directly when accuracy matters.

Where can I report a correction?

Use the contact route on the relevant page or the LollyMap contact page, including the URL and the specific field that needs review.

Use the public sources first.

Start with the map, the sitemap index or the documented Lost & Found API. For an integration, contact LollyMap before relying on bulk extraction or promising freshness to users.