WritersLogic Verifiable AI Agent Hub Geo Axis Check API
The Geo Axis Check API from WritersLogic Verifiable AI Agent Hub — 1 operation(s) for geo axis check.
Work with this as data
Every API here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for apis
7 MCP tools reach this
find_apisBrowse and filter every API in the catalog.get_api_artifactsOne API's artifacts, grouped by type.get_openapiThe primary OpenAPI for this API.find_similar_apisAPIs that look like this one.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This API
curl "https://apis.io/api/v1/apis/writerslogic-com:writerslogic-com-geo-axis-check-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.
OpenAPI Specification
openapi: 3.2.0
info:
title: WritersLogic Verifiable AI Agent Hub Geo Axis Check API
version: 2.0.0
description: Pay-per-call agents settled in USDC on Base via x402. Every response carries a signed provenance envelope.
contact:
name: WritersLogic
url: https://writerslogic.com/agents
email: agents@writerslogic.com
servers:
- url: https://agents.writerslogic.com
tags:
- name: Geo Axis Check
paths:
/api/v1/geo-axis-check:
post:
operationId: geo_axis_check
summary: Coordinate axis-order and unit check from a CRS and its area of use
description: 'Checks up to 1000 coordinate pairs (or one bounding box) against the EPSG coordinate system you name, for agents handling GIS or map data: it flags longitude/latitude swaps, degrees supplied where metres are expected (or the reverse), values outside the CRS''s area of use, and inverted bounds, with the point index and values. It does not reproject, geocode, validate geometry topology or datum, or judge accuracy. Projected systems other than EPSG:3857 have no projection math here, so only unit mix-ups are detected for them and a clean result is `unknown`, not `pass`.
Price: 0.005 USDC on Base (x402).'
x-x402-price-usdc: '0.005'
x-x402-amount: '5000'
x-payment-info:
protocols:
- x402
price:
mode: fixed
currency: USD
amount: '0.005'
x-audience: developer
x-sample-url: https://agents.writerslogic.com/api/v1/samples/geo-axis-check
security:
- x402: []
- apiKey: []
requestBody:
required: true
content:
application/json:
schema:
type: object
additionalProperties: false
required:
- crs
properties:
crs:
type: string
maxLength: 80
description: EPSG code in any common form (EPSG:4326, 4326, urn:ogc:def:crs:EPSG::4326) or CRS84. See versions for the snapshot of known codes; others return unknown unless areaOfUse is supplied.
coordinates:
type: array
maxItems: 1000
items:
type: array
minItems: 2
maxItems: 2
items:
type: number
description: '[first, second] pairs exactly as they appear in the data.'
bounds:
type: array
minItems: 4
maxItems: 4
items:
type: number
description: '[minFirst, minSecond, maxFirst, maxSecond] in the data''s own order; its two corners are checked like points and min must not exceed max.'
declaredOrder:
type: string
enum:
- lon-lat
- lat-lon
- easting-northing
- northing-easting
description: 'What the data claims: lon-lat or easting-northing means the first value is the east axis; lat-lon or northing-easting means north first. Default: the CRS''s EPSG authority order (CRS84: lon-lat).'
areaOfUse:
type: array
minItems: 4
maxItems: 4
items:
type: number
description: '[south, west, north, east] degrees; overrides the snapshot for a geographic CRS or supplies one for an unknown geographic code.'
example:
crs: EPSG:4326
coordinates:
- - 51.5074
- -0.1278
- - -0.1278
- 51.5074
- - 4500000
- 5600000
declaredOrder: lat-lon
responses:
'200':
description: Paid result with provenance
content:
application/json:
schema:
type: object
properties:
data:
type: object
properties:
status:
type: string
enum:
- pass
- fail
- unknown
- unsupported
description: 'pass: every rule held. fail: a rule was violated (see witnesses). unknown: the input lacks the evidence to decide. unsupported: outside what this engine covers. Missing evidence is never a pass.'
crs:
type: object
properties:
code:
type: string
name:
type: string
geographic:
type: boolean
authorityOrder:
type: string
unit:
type: string
areaOfUse:
type: array
items:
type: number
interpretedOrder:
type: string
description: The order used to read the pairs.
points:
type: array
items:
type: object
properties:
index:
type: integer
source:
type: string
verdict:
type: string
enum:
- ok
- ok-ambiguous
- swapped
- swap-suspected
- outside-area
- out-of-range
- units-metres
- units-degrees
- unchecked
description: 'ok-ambiguous: valid as given and also valid swapped, so order cannot be confirmed from values.'
counts:
type: object
description: Points per verdict.
witnesses:
type: array
items:
type: object
properties:
ruleId:
type: string
detail:
type: string
path:
type: string
description: JSON pointer or dotted path into the input.
offset:
type: integer
index:
type: integer
expected:
description: What the rule required.
actual:
description: What the input had.
versions:
type: object
description: Every semantic dependency of this answer (engine, tables and their as-of dates, tokenizer, calendar, rounding profile).
limits:
type: array
items:
type: string
deterministic:
type: boolean
description: 'Always true: pure code, no model.'
_provenance:
type: object
description: C2PA-aligned manifest and W3C VC 2.0 (eddsa-jcs-2022) issued by the hub DID; verify at POST /api/v1/verify-provenance
required:
- data
- _provenance
'400':
description: Invalid request (no payment consumed)
content:
application/json:
schema:
type: object
properties:
error:
type: string
code:
type: string
'401':
description: Invalid X-API-KEY
content:
application/json:
schema:
type: object
properties:
error:
type: string
code:
type: string
'402':
description: Payment required or invalid
content:
application/json:
schema:
type: object
description: x402 v2 PaymentRequired (also base64 in the PAYMENT-REQUIRED header)
properties:
x402Version:
type: integer
error:
type: string
code:
type: string
resource:
type: object
accepts:
type: array
items:
type: object
extensions:
type: object
'502':
description: Upstream failure; the payment is released or not settled
content:
application/json:
schema:
type: object
properties:
error:
type: string
code:
type: string
tags:
- Geo Axis Check
components:
securitySchemes:
x402:
type: apiKey
in: header
name: PAYMENT-SIGNATURE
description: x402 v2 payment payload (base64) sent after a 402 challenge
apiKey:
type: apiKey
in: header
name: X-API-KEY