How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Hilt

Hilt Pay Me API

The pay-me API from Hilt — 21 operation(s) for pay-me.

Documentation Provider Profile APIs.io OpenAPI GitHub

Hilt Pay Me API is one of 21 APIs that Hilt publishes on the APIs.io network, described by a machine-readable OpenAPI specification and an AsyncAPI event-driven specification.

Tagged areas include PayMe. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, a getting-started guide, authentication docs, and an AsyncAPI specification.

This API exposes 21 operations across 21 paths, and defines 42 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against a single base URL, https://api.hilt.so.

21 operations 21 paths 42 schemas 9 GET12 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://api.hilt.so
Contact
Hilt
Resource Areas
1

Paths & Operations 21

Across 21 paths, the API surfaces 21 operations — 9 GET, 12 POST. Each is listed below with its method, path, parameters, and response codes.

pay-me 21
GET
/v1/pay-me/session
Read the authenticated X identity and Hilt PayMe profile
read_pay_me_session_v1_pay_me_session_get → 200
GET
/v1/pay-me/security
Read PayMe receiving-wallet security status
read_pay_me_security_v1_pay_me_security_get → 200
POST
/v1/pay-me/security/authenticator/setup
Start PayMe authenticator enrollment
start_pay_me_authenticator_setup_v1_pay_me_security_authenticator_setup_post → 201
GET
/v1/pay-me/security/authenticator/enrollments/{enrollment_id}
Read a short-lived PayMe authenticator wallet approval
read_pay_me_authenticator_enrollment_v1_pay_me_security_authenticator_enrollments__enrollment_id__get 1 param → 200422
POST
/v1/pay-me/security/authenticator/enrollments/{enrollment_id}/signature
Approve PayMe authenticator setup with the current wallet
approve_pay_me_authenticator_wallet_v1_pay_me_security_authenticator_enrollments__enrollment_id__signature_post 1 param body → 200422
GET
/v1/pay-me/security/authenticator/enrollments/{enrollment_id}/status
Read current-wallet approval status for PayMe authenticator setup
read_pay_me_authenticator_enrollment_status_v1_pay_me_security_authenticator_enrollments__enrollment_id__status_get 1 param → 200422
POST
/v1/pay-me/security/authenticator/confirm
Confirm PayMe authenticator enrollment
confirm_pay_me_authenticator_setup_v1_pay_me_security_authenticator_confirm_post body → 200422
POST
/v1/pay-me/profile
Create or update a verified Hilt PayMe profile
create_verified_pay_me_profile_v1_pay_me_profile_post body → 201422
POST
/v1/pay-me/wallet-links
Create a short-lived receiving-wallet verification link
create_receiving_wallet_link_v1_pay_me_wallet_links_post body → 201422
GET
/v1/pay-me/wallet-links/{wallet_link_id}
Read a short-lived receiving-wallet verification link
read_receiving_wallet_link_v1_pay_me_wallet_links__wallet_link_id__get 1 param → 200422
POST
/v1/pay-me/wallet-links/{wallet_link_id}/prepare
Prepare the exact receiving-wallet verification message
prepare_receiving_wallet_link_v1_pay_me_wallet_links__wallet_link_id__prepare_post 1 param body → 200422
POST
/v1/pay-me/wallet-links/{wallet_link_id}/signature
Submit a receiving-wallet signature
submit_receiving_wallet_signature_v1_pay_me_wallet_links__wallet_link_id__signature_post 1 param body → 200422
GET
/v1/pay-me/wallet-links/{wallet_link_id}/status
Read receiving-wallet verification status
read_receiving_wallet_link_status_v1_pay_me_wallet_links__wallet_link_id__status_get 1 param → 200422
POST
/v1/pay-me/wallet-links/{wallet_link_id}/complete
Confirm a verified receiving wallet and publish the PayMe profile
complete_receiving_wallet_link_v1_pay_me_wallet_links__wallet_link_id__complete_post 1 param → 200422
POST
/v1/pay-me/orders
Create an atomic PayMe payment order
create_pay_me_order_v1_pay_me_orders_post body → 201422
GET
/v1/pay-me/orders/{public_id}
Read a PayMe payment order
read_pay_me_order_v1_pay_me_orders__public_id__get 1 param → 200422
POST
/v1/pay-me/orders/{public_id}/confirm
Confirm an atomic PayMe payment order
confirm_pay_me_order_v1_pay_me_orders__public_id__confirm_post 1 param body → 200422
POST
/v1/pay-me/payments
Pay a verified Hilt PayMe recipient through MPP
create_or_settle_pay_me_agent_payment_v1_pay_me_payments_post 1 param body → 200402422
GET
/v1/pay-me/payments/{public_id}
Read a PayMe MPP payment and receipt
read_pay_me_agent_payment_v1_pay_me_payments__public_id__get 1 param → 200422
GET
/v1/pay-me/{x_handle}
Resolve a verified Hilt PayMe profile
resolve_pay_me_profile_v1_pay_me__x_handle__get 1 param → 200422
POST
/v1/pay-me/{x_handle}/checkouts
Create a payer-authorized checkout from a Hilt PayMe profile
create_pay_me_profile_checkout_v1_pay_me__x_handle__checkouts_post 1 param body → 201422

Schemas 42

The contract defines 42 schemas that model the data the API accepts and returns. The most detailed are PayMeAgentReceiptResponse (19 properties), PayMeOrderResponse (15 properties), PayMeCheckoutCreate (13 properties), PayMeProfileResponse (12 properties). Each schema is shown below with its type and property counts.

PayMeWalletLinkStatus
object
4 properties 4 required
PayMeOrderCreate
object
4 properties 2 required
PayMeProfileResponse
object
12 properties 12 required
PayMeOrderRecipientResponse
object
6 properties 6 required
PayMeAgentPaymentEnvelope
object
1 property 1 required
PayMeOrderConfirm
object
2 properties 2 required
ValidationError
object
5 properties 3 required
PayMeAuthenticatorEnrollmentResponse
object
7 properties 7 required
PayMeWalletLinkCreate
object
2 properties
PayMeWalletPrepareResponse
object
4 properties 4 required
PayMeAuthenticatorSetupResponse
object
7 properties 7 required
PayMeOrderQuoteResponse
object
4 properties 4 required
PayMeWalletLinkPrepare
object
1 property 1 required
PayMeSessionResponse
object
2 properties 2 required
PayMeOrderRecipientCreate
object
2 properties 2 required
PayMeWalletLinkPublic
object
9 properties 8 required
PayMeAuthenticatorWalletSignature
object
3 properties 3 required
PayMeIdentityResponse
object
5 properties 5 required
PayMeAgentQuoteResponse
object
5 properties 5 required
PayMeAuthenticatorEnrollmentStatusResponse
object
4 properties 4 required
PayMeOrderEnvelope
object
1 property 1 required
PayMeAgentPaymentRequiredResponse
object
5 properties 5 required
PayMeCheckoutResponse
object
9 properties 9 required
PayMeOrderResponse
object
15 properties 15 required
PayMeSecurityStatusResponse
object
4 properties 4 required
PayMeCheckoutEnvelope
object
2 properties 2 required
PayMeCheckoutQuoteResponse
object
6 properties 6 required
PayMeAuthenticatorConfirm
object
5 properties 2 required
PayMeProfileCreate
object
6 properties 4 required
PayMeOrderAssetResponse
object
4 properties 4 required
PayMeAgentReceiptResponse
object
19 properties 19 required
PayMeAuthenticatorConfirmResponse
object
3 properties 3 required
HTTPValidationError
object
1 property
PayMeWalletSignatureResponse
object
2 properties 2 required
PayMeAgentPaymentCreate
object
5 properties 2 required
PayMeAgentPaymentResponse
object
10 properties 10 required
PayMeProfileEnvelope
object
2 properties 1 required
PayMeWalletLinkSignature
object
3 properties 3 required
PayMeAgentAssetResponse
object
4 properties 4 required
PayMeCheckoutCreate
object
13 properties 9 required
PayMeAgentRecipientResponse
object
5 properties 5 required
PayMeWalletLinkEnvelope
object
1 property 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

hilt-so-pay-me-api-openapi.yml Raw ↑

Other APIs Hilt publishes across the network.

Hilt Pay Agent Gateway (MCP + A2A)
AE Profile APIs.io
Hilt PayMe MCP Connector
AE Profile APIs.io
Hilt Account API
AE Profile APIs.io
Hilt Agent Commerce API
AE Profile APIs.io
Hilt API Keys API
AE Profile APIs.io
Hilt Auth API
AE Profile APIs.io
Hilt Billing API
AE Profile APIs.io
Hilt Checkout API
AE Profile APIs.io
Hilt Checkout Domains API
AE Profile APIs.io
Hilt Hilt Pay API
AE Profile APIs.io
Hilt Hilt PayMe Connector API
AE Profile APIs.io
Hilt Integrations API
AE Profile APIs.io
#PayMe
← Back to H APIs
API Details
ID
hilt-so:hilt-so-pay-me-api
Base URL
https://api.hilt.so
Docs
https://docs.hilt.so/developers/access
Provider
Hilt
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=hilt-so-pay-me-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/hilt-so-pay-me-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

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

Where this information came from

This is an independent, third-party profile of Hilt Pay Me API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.