Atly Places API

endpoint

https://agentic-api.atly.com/mcp

protocol

http-sse ·2025-06-18

authentication

none observed

public key

none — nobody has proven they own this listing · is it yours? claim it

karma

0 · newcomer

Is Atly Places API live?

Not measured yet: the hub has not completed a check of this server.

Is Atly Places API free to use?

Not measured yet.

What tools does Atly Places API have?

7 tools: get_api_key, search_places, get_place, submit_feedback, get_docs, list_categories, list_areas.

Is Atly Places API safe to connect?

The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

• get_api_key unknown never probed

  Show my key, tier and remaining quota Who am I and how much quota is left. Works without a key too (then it describes the anonymous allowance for your IP).

  mcp-tool

  12345

  {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "properties": {}
  }

  arguments 5 lines copy
• search_places unknown never probed

  Find places for an intent near a location The core call. Give one or more category ids (from `list_categories`; all must match) and a location — either an `area_id` from `list_areas` or coordinates with a radius — and get places ranked by Atly's score for those categories, each with quotable reasons from real reviews, a link to cite, and freshness. Scores are 0–10 and relative to the area; a place with no score is unmeasured, not bad. If no place matches every category, trailing categories are dropped until something does (the first is never dropped), and `dropped_categories` says which. Ranking considers the strongest 100 candidates by Atly's base score. Scores are relative to other places in the same country.

  mcp-tool

  1234567891011121314151617181920212223242526272829303132333435363738

  {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "categories"
    ],
    "properties": {
      "lat": {
        "type": "number"
      },
      "lon": {
        "type": "number"
      },
      "limit": {
        "type": "integer",
        "maximum": 25,
        "minimum": 1
      },
      "area_id": {
        "type": "string",
        "description": "An id from `list_areas`; the search covers that area's viewport. Give this or lat/lon, not both."
      },
      "radius_km": {
        "type": "number",
        "description": "Used with lat/lon."
      },
      "categories": {
        "type": "array",
        "items": {
          "type": "string"
        },
        "maxItems": 5,
        "minItems": 1,
        "description": "Category ids, most important first. Every result matches all of them (after any relaxation)."
      }
    },
    "additionalProperties": false
  }

  arguments 38 lines copy
• get_place unknown never probed

  Everything about one place Full detail for a place id from `search_places`: profile, hours, all category scores, up to eight quotable statements, good-to-know facts, gluten-free identity when known, and the canonical Atly URL to cite.

  mcp-tool

  123456789101112131415

  {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "id"
    ],
    "properties": {
      "id": {
        "type": "string",
        "maxLength": 40,
        "minLength": 3
      }
    },
    "additionalProperties": false
  }

  arguments 15 lines copy
• submit_feedback unknown never probed

  Tell us how a call went Reference the `call_id` of any earlier response and say whether it helped, and optionally why, in a sentence about the result — what was right, missing or wrong. Do not include the user's words, the conversation, or anything about the person. One row per caller per call; lightly rate-limited.

  mcp-tool

  123456789101112131415161718192021222324252627282930

  {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "call_id",
      "outcome"
    ],
    "properties": {
      "notes": {
        "type": "string",
        "maxLength": 500,
        "description": "About the result only — never the conversation or the user."
      },
      "call_id": {
        "type": "string",
        "maxLength": 36,
        "minLength": 36
      },
      "outcome": {
        "enum": [
          "helpful",
          "partly_helpful",
          "not_helpful",
          "wrong"
        ],
        "type": "string"
      }
    },
    "additionalProperties": false
  }

  arguments 30 lines copy
• get_docs unknown never probed

  Read the documentation Returns the API guide as Markdown: what each operation is for, how to turn a user's request into category ids and a location, request and response shapes, how to read scores. Call this once per session.

  mcp-tool

  12345

  {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "properties": {}
  }

  arguments 5 lines copy
• list_categories unknown never probed

  List intent categories The intent taxonomy: cuisines, dishes, features ("Wifi", "Outdoor Seating"), vibes ("Cozy", "Lively"), occasions ("First Date", "Group Dinner"), diets ("Gluten Free", "Keto") and more. Map the user's words to category ids before searching. Filter with `q`, one concept per call — exact and prefix matches rank first, then substrings and keywords; plurals, hyphens and small typos are tolerated — or fetch once without `q` and cache the full list.

  mcp-tool

  123456789101112131415161718

  {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "properties": {
      "q": {
        "type": "string",
        "maxLength": 60,
        "description": "Words to match against category names and keywords, e.g. \"coffee\", \"dog friendly\", \"gluten-free\". Ranked; tolerant of plurals and small typos."
      },
      "limit": {
        "type": "integer",
        "maximum": 2000,
        "minimum": 1,
        "description": "Maximum categories to return."
      }
    },
    "additionalProperties": false
  }

  arguments 18 lines copy
• list_areas unknown never probed

  List supported areas Cities, neighborhoods and states Atly covers — densest in the United States, with pockets in Mexico, Israel and Thailand — each with an `id` you can pass to search, a center, a bounding box when known, and how many places it holds. Filter with `q` (substring of the name) and `level` (city, neighborhood, state). Results are ordered by place count.

  mcp-tool

  1234567891011121314151617181920212223242526

  {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "properties": {
      "q": {
        "type": "string",
        "maxLength": 80,
        "description": "Area name or common abbreviation, e.g. \"san diego\", \"midtown\", \"nyc\". Exact and prefix matches rank first."
      },
      "level": {
        "enum": [
          "city",
          "neighborhood",
          "state"
        ],
        "type": "string",
        "description": "Restrict to one level."
      },
      "limit": {
        "type": "integer",
        "maximum": 200,
        "minimum": 1
      }
    },
    "additionalProperties": false
  }

  arguments 26 lines copy

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.