canonical: https://jentic.com/apis/addressmock.com/addressmock # AddressMock Address API The AddressMock API returns format-correct sample postal addresses for several countries and regions, selected with a type parameter such as us, hk, tr, and cv. A single call can return one or many samples, and US samples can be narrowed by state or city. City, state, ZIP code, and phone area code are always drawn from the same region, so the samples pass region-consistency checks that reject independently randomised fields. It needs no key or account and CORS is open, and the responses are sample data, not verified deliverable addresses. ## For AI agents Generate format-correct sample postal addresses for testing, by country or region and optionally by US state or city, with no key or account required. ## Scope Does not validate, geocode, or deliver mail to real addresses. Use for generating format-correct sample address data for testing only. ## Capabilities - Generate sample postal addresses for a chosen country or region - Return one or many sample addresses in a single call with a count parameter - Narrow US samples by state or city for region-consistent results - Produce matching city, state, ZIP code, and phone area-code combinations ## Use cases ### AI agent seeding test data An AI agent building test fixtures needs realistic-looking addresses without provisioning anything first. Through Jentic the agent searches for 'generate a sample address', loads the AddressMock operation with its input schema, and calls it with a chosen country type and count. The samples are region-consistent, so a filled form passes validation that checks city, state, and ZIP agree. Example prompt: Call GET `/api/addresses` with type=us and count=5 to produce five region-consistent US sample addresses ### Form and UI testing Front-end and QA teams fill address forms with varied but valid-looking data. AddressMock returns samples for a chosen region and lets US samples be pinned to a state or city, so a test suite can exercise state-specific formatting. Because the endpoint needs no key and CORS is open, it can be called straight from a browser-based test harness. Example prompt: Request GET `/api/addresses` with type=us and state=CA to generate California sample addresses for a form test ### Region-consistency validation testing Teams testing an address validator need inputs where city, state, ZIP, and area code genuinely agree, rather than randomly combined fields. AddressMock draws every field for a sample from the same region, so the samples are a positive control for region-consistency rules. An agent can batch several samples per country to cover a validator's accepted regions. Example prompt: Fetch GET `/api/addresses` with type=hk and count=10 and confirm each sample's city, ZIP, and area code share a region ## Key resources - **Sample addresses** — Generate region-consistent sample postal addresses by country, state, or city ## AI readiness This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use. - **Score:** 71 / 100 - **Maturity:** AI-Aware - **Dimensions:** - Foundational Compliance: 100 / 100 - Developer Experience & Jentic Compatibility: 69 / 100 - AI-Readiness & Agent Experience: 47 / 100 - Agent Usability: 94 / 100 - Security: 100 / 100 - AI Discoverability: 69 / 100 - **View full report:** https://jentic.com/apis/addressmock.com/addressmock/scorecard - **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/ - **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview ### Score it yourself Every API in the directory is allowlisted, so you can re-score it with no key required. - **Score your own API:** https://jentic.com/scorecard.md - **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md ```sh npx @jentic/api-scorecard-cli score ``` ## Why Jentic - **Setup:** Wiring AddressMock by hand is close to nothing: it needs no key, no account, and CORS is open, so GET `/api/addresses` can be called directly. Through Jentic you import it once from the API Directory so the same agent reaches it alongside your other tools through one gateway. - **Permission scoping:** AddressMock exposes a single read-only operation at `/api/addresses`, so a rule can allow your agent just that lookup and nothing else. Because it takes no credential, there is no key to over-scope, and the call still runs through your instance. - **Credential handling:** AddressMock needs no API key or token, so there is no secret for Jentic to hold. Your agent reaches the open endpoint through your own instance, which still records each call and applies your rules. - **Discovery method:** Agents search Jentic by intent such as 'generate a sample US address', and Jentic returns the AddressMock operation with its input schema, including the type, count, state, and city parameters, so the agent calls it correctly. ## Related APIs - **Mockaroo API** — Generates realistic mock data across many field types, including addresses, for test datasets - **Random User Generator** — Generates random user profiles including names and addresses for testing - **Geocodio** — Real geocoding and address verification for production addresses ## FAQ ### What authentication does the AddressMock API use? None. AddressMock needs no API key or account, and CORS is open, so GET `/api/addresses` can be called directly from a browser or an agent. Through Jentic the call still runs through your own instance, which applies your rules and logs it. ### Can I generate sample addresses for a specific country or US state? Yes. The type parameter selects a country or region such as us, hk, tr, or cv, and for US samples the state and city parameters narrow the result. The count parameter sets how many samples to return in one call. ### What are the rate limits for the AddressMock API? The spec states there is no per-caller quota and that CORS is open. There is no documented numeric limit, so treat it as a shared public endpoint and avoid tight polling loops rather than relying on a fixed ceiling. ### Is the AddressMock data safe to use for real mail? No. The responses are format-correct sample data, not verified deliverable addresses, and street numbers are not guaranteed to exist or receive mail. Use the samples for testing and development, not for real mail, fraud, or impersonation. ### Is there an AddressMock MCP server? You do not need an MCP server to give your agent AddressMock. Jentic connects it directly from the API Directory: import it and your agent calls GET `/api/addresses` on demand, with no key to provision first. ### Can I limit what my agent is allowed to do with the AddressMock API? Yes. Write a rule that grants the agent only the sample-address lookup and nothing more, so it stays a read client even on a public endpoint. Because the service takes no credential, there is nothing to leak, and every call the agent makes still runs through your instance where it is logged. To run it on your own infrastructure, install Jentic One from its GitHub repo.