APIAI AgentsDevelopersProduct Launch

By Township Canada

townshipcanada.com Is Now Agent-Readable: How AI Agents Find and Use the API

AI agents can read townshipcanada.com as markdown and find the API, its OpenAPI spec, an agent skill and access steps without custom setup.

Suppose you are building an AI agent for an oil and gas company's field planning team. A planner types "Get me GPS coordinates for the well site at 6-32-48-7-W5" into the agent. The agent has never heard of Township Canada. Until recently, you would have had to find the API yourself, read the docs, and write the endpoint, parameters and authentication into the agent's prompt or tools by hand.

townshipcanada.com now publishes what an agent needs to do most of that on its own: a machine-readable map of the API, a skill file that explains how to call it, plain instructions for getting access, and a markdown version of every public page. This post walks through what we published, how an agent uses it, and the one step that still needs a person.

What an agent could not do before

A web page built for people is a poor source for an agent. The layout, menus and scripts around the content cost tokens and hide the parts that matter. On our API docs page, the code samples were rendered in the browser, so a crawler that did not run JavaScript saw empty blocks where the examples should have been.

There was also no standard place to look. An agent that wanted to know whether townshipcanada.com had an API, where its specification lived, and how to authenticate had to guess at URLs or read marketing pages. As a result, the integration work fell back on the developer.

What changed

Most of these follow a published standard or proposal, so an agent that already knows the convention needs no instructions written for Township Canada.

  • Markdown for any public page. Request any public page with the header Accept: text/markdown and you get the page content as markdown, with front matter for the title, description and URL. The response carries Vary: Accept and an approximate token count in x-markdown-tokens. The signed-in app, the login page and the private API routes never convert.
  • /llms.txt. A curated entry point: what Township Canada does, links to pricing, the converters, every API reference page, and the discovery files below.
  • API catalog at /.well-known/api-catalog. An RFC 9727 linkset that names the API hosts (developer.townshipcanada.com and maps.townshipcanada.com) and points each one to the OpenAPI specification, the human docs and the status page.
  • Homepage Link headers. The homepage response points to the API catalog, the OpenAPI spec (service-desc), the docs page (service-doc) and llms.txt (describedby), so an agent that only fetches / still finds them.
  • An agent skill. /.well-known/agent-skills/index.json lists a township-canada-api skill, and its SKILL.md explains the survey systems, the endpoints, the error codes, and when to use each one.
  • An ai-catalog manifest at /.well-known/ai-catalog.json, also linked from every page's <head>.
  • /auth.md. How an agent and the software it runs get access, written for an agent to read.
  • Server-rendered code samples on the API docs, so the markdown version includes them.

On November 16, 2026, the isitagentready.com scanner rated townshipcanada.com Level 5 (Agent-Native), its highest level.

The field planning agent, step by step

Back to the planner's request. An agent that follows these conventions can work through it like this:

  1. It fetches the homepage and reads the Link header, or goes straight to /.well-known/api-catalog. Both lead to https://townshipcanada.com/openapi.yaml and the docs.
  2. It finds the township-canada-api skill in the skills index and reads SKILL.md. The skill tells it that 6-32-48-7-W5 is a DLS legal subdivision (LSD 6 of section 32, township 48, range 7, west of the 5th meridian) and that the Search API converts it.
  3. It reads /auth.md and learns that the Search API needs an API key in the X-API-Key header.
  4. It calls the Search API with the key:
curl "https://developer.townshipcanada.com/search/legal-location?location=6-32-48-7-W5" \
  -H "X-API-Key: $TOWNSHIP_CANADA_API_KEY"

The response is a GeoJSON FeatureCollection with two features: the LSD boundary and its centroid. For this LSD, just south of Drayton Valley, the centroid is about 53.1833, -114.9919. GeoJSON lists coordinates as longitude, latitude, so the agent should swap them before quoting a latitude and longitude to the planner. The centroid is the centre of the 40-acre LSD, not a surveyed wellhead.

The step that still needs a person

There is no self-service sign-up for agents. A person signs in at townshipcanada.com, subscribes to the API they need in the developer portal, and gives the key to the agent as a secret. /auth.md and the skill both say this, so a well-behaved agent asks for the key instead of trying to register itself. Each API (Search, Autocomplete, Batch, the Ag and Energy report APIs, and the map tile APIs) is its own subscription with its own key.

This is deliberate. A key is tied to a paid plan and a monthly request quota, and a request over the quota returns 429. The agent can discover everything else, but someone accountable for the bill decides which API it may call.

If your agent works inside ChatGPT or Claude rather than as your own code, there is a second path that does not use API keys. The Township Canada connector for ChatGPT and Claude signs in with a person's Pro or Business account over OAuth, and /auth.md covers that path too.

What the robots.txt Content Signals say

/robots.txt now declares Content Signals for all crawlers, including GPTBot, ClaudeBot, PerplexityBot and Google-Extended:

Content-Signal: search=yes, ai-input=yes, ai-train=no

In plain terms, search engines may index the site, and AI tools may read pages to answer a question. The site's content may not be used to train models. Two crawlers, Bytespider and CCBot, are blocked from the whole site.

How to get started

For a hand-built integration instead, the API integration guide covers the same endpoints for people.