Merit Systems · Agentic Access

Merit Systems Agentic Access

x-agentic-access generated

Merit Systems exposes 9 API operations that an AI agent could call, of which 2 are state-changing ‘acting’ operations. This is a recommended x-agentic-access execution contract — the scope, audience, consequence tier, short-lived token constraints, and escalation each action should carry before it is handed to an autonomous agent.

By consequence: 7 read, 1 write, and 1 physical.

Contracts are classified heuristically from the provider’s OpenAPI and refresh on every APIs.io network build; audience is bound per deployment. The model follows Curity’s Access Intelligence (apidays Munich 2026). Browse every provider’s agent contracts at agentic-access.apis.io.

CompanyAgentic CommercePaymentsx402MicropaymentsMCPStablecoinsAPI DiscoveryOpen-SourceDeveloper Tools
Operations: 9 Acting: 2 Human-in-the-loop: 0 Method: generated

By consequence

read 7 write 1 physical 1

Source

Agentic Access

Raw ↑
generated: '2026-07-20'
method: generated
source:
  - openapi/merit-systems-merit-api-openapi.yml
  - openapi/merit-systems-agentcash-openapi.json
note: >-
  Recommended x-agentic-access execution contracts generated by classifying each
  OpenAPI operation (Curity "Access Intelligence" model). A governance starting
  point, not an authoritative provider claim. audience is left null to bind per
  deployment.
audience: null
summary:
  operations: 9
  by_action_class:
    connected: 7
    acting: 2
  by_consequence:
    read: 7
    write: 1
    physical: 1
  human_in_the_loop: 1
operations:
  - operation: getUserBalanceByLogin
    api: Merit Systems API
    action_class: connected
    consequence: read
    token: { ttl_seconds: 3600 }
  - operation: getUserBalanceByGithubId
    api: Merit Systems API
    action_class: connected
    consequence: read
    token: { ttl_seconds: 3600 }
  - operation: getRepoBalanceByName
    api: Merit Systems API
    action_class: connected
    consequence: read
    token: { ttl_seconds: 3600 }
  - operation: getRepoBalanceByRepoId
    api: Merit Systems API
    action_class: connected
    consequence: read
    token: { ttl_seconds: 3600 }
  - operation: getPaymentsBySender
    api: Merit Systems API
    action_class: connected
    consequence: read
    token: { ttl_seconds: 3600 }
  - operation: search
    api: AgentCash
    action_class: connected
    consequence: read
    token: { ttl_seconds: 3600 }
    note: Natural-language discovery query; no side effects.
  - operation: organizations
    api: AgentCash
    action_class: connected
    consequence: read
    token: { ttl_seconds: 3600 }
  - operation: invite-codes
    api: AgentCash
    action_class: acting
    consequence: write
    token: { ttl_seconds: 900 }
    audit: required
  - operation: send
    api: AgentCash
    action_class: acting
    consequence: physical
    reason: Transfers USDC to an arbitrary address (money movement).
    token: { ttl_seconds: 300, exchange: true }
    purpose_required: true
    audit: required
    human_in_the_loop: recommended

Work with this as data

Every access contract here is available over the APIs.io API and to AI agents over MCP. Agentic Access is not yet its own endpoint on the v1 API. Reach it through catalog search and the tag graph, or the MCP server.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for agentic access

3 MCP tools reach this
  • 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
Search the catalog
curl "https://apis.io/api/v1/search?q=merit-systems-agentic-access&limit=10"
Everything under a tag
curl "https://apis.io/api/v1/tags/merit-systems-agentic-access"

Discovery needs no key. Ratings and market analysis are Pro.

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.