Geopipe

Geopipe uses AI and machine learning to build game-ready digital twins of real-world cities and environments. It ingests raw sensor data (imagery and laser scans) and reconstructs regions as semantically-modeled, multi-level-of- detail 3D models that developers stream or download into games, simulations, training, architecture, and metaverse applications without any manual 3D modeling. Delivery is through Cesium 3D Tiles streaming for Unity and Unreal Engine, downloadable 3D meshes in common file formats, ready-to-use Unity Asset Store packs, and a first-party Unity SDK, backed by an open-source geospatial and 3D-tiles toolchain on GitHub. Founded in New York City by Christopher Mitchell and Thomas Dickerson and backed by Techstars.

Geopipe is profiled on the APIs.io network. Tagged areas include Company, 3D, Digital Twin, Geospatial, and Gaming.

Geopipe’s developer surface includes signup flow, engineering blog, and 7 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

8.0/100 minimal ▬ flat Agent 10/100 agent aware Front door AI 3/6 light Heartbeat 0/100 dormant saas Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

0 APIs 1 MCP Servers

Company 3D Digital Twin Geospatial Gaming Simulation Unity Unreal Engine Cesium3D TilesMetaverse Maps

Kin Score

Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0

Composite quality — 8.0/100 · minimal

Contract Quality 0.0 / 21

Developer Ergonomics 1.6 / 17

Access Clarity 1.1 / 17

Operational Transparency 0.3 / 11

Contract Governance 0.0 / 10

Discoverability 5.0 / 9

Regulatory Posture 0.9 / 15

Agent readiness — 10/100 · agent aware

Machine-Readable Contract 0 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 12 / 12

Machine-Readable Auth 0 / 10

Idempotency 0 / 9

Stable Error Semantics 0 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 0 / 7

Typed Event Surface 0 / 6

Agent Skills 0 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 5 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.

The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/geopipe/"><img src="https://apis.io/badge/geopipe/card.svg" alt="Geopipe on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

Machine-Readable Contract +18 pts — api_specs includes an OpenAPI document
Agentic Access Contract +10 pts — agentic_access artifact present (x-agentic-access), graded by author
Machine-Readable Auth +10 pts — a served openid-configuration/oauth-authorization-server carrying `issuer` (served), else the securitySchemes class in the provider OpenAPIs — bound (mutualTLS, DPoP, Signature) > negotiable (oauth2 authorizationCode/clientCredentials, openIdConnect) > bearer (http bearer, apiKey)
Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
Stable Error Semantics +8 pts — OpenAPI $refs a shared error schema across 4xx/5xx responses (verified), else common[].type includes ErrorCatalog / ErrorCodes / DeclineCodes
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0

12 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Contract Quality scores 0.0 — up to +25.0 composite points
Access Clarity scores 6.6 — up to +18.7 composite points
Developer Ergonomics scores 9.5 — up to +18.1 composite points

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/geopipe/apis.yml: open an issue on github.com/api-evangelist/geopipe to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Markets this provider is in provisional

The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.

Market	Position	Depth	Registered MCP server	Declares compatibility
XR & Graphics (XR, 3D, GPU graphics)	undeclared	-	-	-
Overture Maps Foundation (members + data contributors)	undeclared	-	-	-

Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.

Standards implemented 2

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

Model Context Protocol (MCP)

measured — observed by APIs.io (verified)

Universal Commerce Protocol (UCP)

measured — observed by APIs.io (wix)

MCP Servers 1

Model Context Protocol servers that expose these APIs to AI agents.

Geopipe MCP Server

Remote MCP server at www.geopipe.ai over HTTP; 10 tools listed.

MCP SERVER

Security Posture 1

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Geopipe Domain Security

TLSv1.3 · HSTS

SECURITY

Resources

Get Started 1

Portal, sign-up, and the first successful call

SignUp

SignUp

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

LLMsTxt

LLMsTxt

Build 3

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

GitHubOrganization

Packages

Packages

SDKs

SDKs

Access & Security 1

Authentication, authorization, and security posture

DomainSecurity

DomainSecurity

Company 3

The organization behind the API

Website

Website

Blog

Blog

BlogRSS

BlogRSS

Source (apis.yml)

aid: geopipe
name: Geopipe
description: Geopipe uses AI and machine learning to build game-ready digital twins of real-world cities and environments.
  It ingests raw sensor data (imagery and laser scans) and reconstructs regions as semantically-modeled, multi-level-of- detail
  3D models that developers stream or download into games, simulations, training, architecture, and metaverse applications
  without any manual 3D modeling. Delivery is through Cesium 3D Tiles streaming for Unity and Unreal Engine, downloadable
  3D meshes in common file formats, ready-to-use Unity Asset Store packs, and a first-party Unity SDK, backed by an open-source
  geospatial and 3D-tiles toolchain on GitHub. Founded in New York City by Christopher Mitchell and Thomas Dickerson and backed
  by Techstars.
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: false
  label: Hosted service · you call their endpoint
  confidence: medium
  source:
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source:
  - security
  generated: '2026-11-06'
  method: derived
image: https://static.wixstatic.com/media/e35cce_98f6141f448e4a43922e904306a322b2~mv2.png
url: https://raw.githubusercontent.com/api-evangelist/geopipe/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- techstars
x-tier: profiled
x-tier-reason: portfolio-lead
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-07-19'
tags:
- Company
- 3D
- Digital Twin
- Geospatial
- Gaming
- Simulation
- Unity
- Unreal Engine
- Cesium
- 3D Tiles
- Metaverse
- Maps
tags_raw:
- Company
- 3D
- Digital Twins
- Geospatial
- Gaming
- Simulation
- Unity
- Unreal Engine
- Cesium
- 3D Tiles
- Metaverse
- Maps
apis: []
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: Website
  url: https://geopipe.ai/
- type: SignUp
  url: https://cs.geopi.pe/register
- type: Blog
  url: https://geopipe.ai/news
- type: BlogRSS
  url: https://www.geopipe.ai/blog-feed.xml
- type: GitHubOrganization
  url: https://github.com/geopipe
- type: Packages
  url: packages/geopipe-packages.yml
- type: SDKs
  url: https://assetstore.unity.com/publishers/57748
- type: LLMsTxt
  url: llms/geopipe-llms.txt
- type: DomainSecurity
  url: security/geopipe-domain-security.yml
x-enrichment:
  date: '2026-07-19'
  status: backfilled
  pass: local-v1
  note: backfilled from .gitignore signal + verified work evidence

Geopipe API — frequently asked questions

Does Geopipe have an MCP server?

Yes. APIs.io lists 1 MCP server for Geopipe: Remote MCP server at www.geopipe.ai over HTTP; 10 tools listed.

Is the Geopipe API ready for AI agents?

Geopipe has a Kin Score of 8.0 out of 100 (minimal) and an Agent Readiness score of 10.3 (agent-aware), scored by API Evangelist on 2026-11-06.

Work with this as data

Every provider 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 providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
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.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/geopipe"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/geopipe/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/geopipe/evidence"

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.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.