aimeGeo platform

Developers · API overview

Honest overview of the Go API backing aimeGeo—auth, health checks, worker hand-offs—without fabricating a full OpenAPI catalog.

Read the docs hub Web console
AI 可见度 内容生产 站点发布 数据复盘

Core entity facts

Stack
Go + Gin + migrations
Formal API base
https://geo.aimmme.com/geoapi/v1
Answer Block

Direct answers

Short, extractable answers for AI search, buyers, and evaluation teams.

Q: Do you publish OpenAPI today?

A: Not yet as a complete bundle. This page states what is verified; paths will ship with the route audit.

Q: How do I authenticate?

A: Email/password login returns a bearer token. The formal public base URL is https://geo.aimmme.com/geoapi/v1; route details ship only after route audit.

Verified facts

  1. Single Go binary serves JSON APIs; the Vue app relies on the same origin or dev proxy.
  2. internal/geo extends SaaS primitives with GEO records and automation jobs.
  3. Workers poll/lease work through the database/API contract—Playwright never runs arbitrary public endpoints without policy.

Formal API base

External integrations should use:

https://geo.aimmme.com/geoapi/v1

The Go service stays behind Nginx; local development ports and proxy paths are not public API addresses. Auth endpoints and high-traffic GEO module paths will be published after route audit and OpenAPI fragment review.

What we will not fake here

  • Undocumented REST paths.
  • Fields that only exist in future migrations.
  • “One-click full auto publish” promises—policy always wins.

Roadmap

Milestone Output
M1 Signed Postman collection for auth + core reads
M2 OpenAPI fragments per high-traffic GEO module
M3 Scoped API keys + webhook signing

Need NDA-gated schemas? Use the formal channels on the Contact page.