the admission gate

Agent-native must be central.

Ginse exists to help replace incumbent SaaS with agent-native tools. A product is listed only when current public evidence indicates that an agent can complete its central job end to end through an API, CLI or MCP.

  1. Core jobDefine the main outcome customers use the product to achieve—not a peripheral integration.
  2. Directly operableAn agent can invoke that job through a documented API, CLI or MCP surface.
  3. End to endThe machine interface can start, control and obtain the useful result without routine dashboard work.
  4. Public evidenceA reviewer can link to current documentation or a working machine interface that supports the claim.
  5. Human moderationAutomation may admit clear documented cases; human review settles ambiguous centrality, reports and corrections.
  6. Separate rankingEligibility is a gate. AX quality, votes and discussion rank eligible tools; a high score cannot rescue an ineligible product.
  7. Reversible statusIf evidence disappears or the central interface stops working, the listing can return to review or leave public search.

What is not enough by itself

An SDK wrapper, webhook, browser UI, chat box, internal AI feature, agent-themed marketing, or a product that agents can merely use through browser automation does not satisfy this gate on its own.

What a listing means

Admission means the central job appears agent-operable from reviewed evidence. It is not a guarantee of security, uptime, price, legal compliance, or one-for-one replacement of every incumbent feature.

Any language, discoverable by everyone

Products in any language are welcome. Each listing needs a short English name and summary for discovery, while its original name and trustworthy primary evidence stay available for review. We translate for discovery only and exclude peripheral, unverifiable, or incomplete machine interfaces.