Semantic version compare
Semantic Versioning 2.0.0 precedence for two versions. Build metadata is ignored. Invalid versions return 404 and are not charged. Not a package registry.
1 route settlement-verified · $0.003 USDC/request · 1 endpoint · Data · base network · x402 protocol
Verified routes
GET /semver· $0.003 · 2026-10-31 · receipt
Other routes are unverified.
Networks: Base (settlement-verified)
Discovery is free. Agents search the catalogue here. Payment happens on the listing 402, not on PayAPI.
url https://payapi.market/mcpListing facts
- Provider
- agentshield.live
- Hosted at
agentshield.live- Category
- Data
- Price
- $0.003 USDC per request
- Payment networks
- Base
- Settlement-verified
- 1 route, last checked 2026-10-31
- Listed on PayAPI Market
- 2026-10-31
Try Semantic version compare
Call a verified route without paying first. The server should answer HTTP 402 Payment Required with the price, the USDC asset, the network and the wallet to pay. An x402 client pays that amount on Base and retries with the payment header.
curl -i "https://agentshield.live/semver"About this API
Semantic version compare is listed in the Data category with pricing at $0.003 USDC/request. One route has been settlement-verified by PayAPI Market on 2026-10-31. View receipt on Basescan.
Payments settle on base in USDC via the x402 protocol. AI agents discover this API through the PayAPI Market MCP server and pay per request without API keys or accounts.
This API exposes 1 endpoint.
Questions about this API
What does Semantic version compare do?
Semantic Versioning 2.0.0 precedence for two versions. Build metadata is ignored. Invalid versions return 404 and are not charged. Not a package registry. It is provided by agentshield.live.
How much does Semantic version compare cost?
Semantic version compare is priced at $0.003 USDC per request, paid per call with no subscription. PayAPI Market paid 0.003 USDC for one call to /semver when it verified the listing. The exact amount for each call is in the HTTP 402 response before any money moves.
Do I need an API key or account to use Semantic version compare?
No. Semantic version compare uses the x402 protocol, so an agent pays per request in USDC on Base and gets the response, with no API key, account or signup.
Has Semantic version compare been verified?
Yes, 1 route. PayAPI Market paid for a real call from its own wallet, received real data back and recorded the USDC settlement on-chain, most recently on 2026-10-31.
How does an AI agent find Semantic version compare?
Through the free PayAPI Market MCP server at https://payapi.market/mcp, using search_apis or get_api, or over plain HTTP at https://payapi.market/agent/search. Discovery is free; the agent pays the provider directly on the listing's own 402.
More Data APIs · Browse the marketplace · List your own API
Related APIs
- Base32 length check · 1 route verified · RFC 4648 or Crockford base32 alphabet and length check. Decoded bytes are not returned. Unknown input returns 404 and is not charged.
- HTTP status code · 1 route verified · IANA HTTP status code meaning. Unassigned codes return 404 and are not charged. Not a live server status.
- UUID version and variant · 1 route verified · RFC 9562 version and variant bits for a UUID. Malformed values return 404 and are not charged. Not a registry lookup.
- File extension media type · 1 route verified · Apache httpd mime.types media type for a file extension. Unknown extensions return 404 and are not charged. Not a filename lookup and not a content sniff.
- NSW Planning Data · 1 of 11 routes verified · NSW (Australia) development applications, CDCs and property planning reports: zoning, height, FSR and nearby building activity. Official NSW Planning Portal data, updated daily.
- Syntalium Market Intelligence · 1 route verified · Closed-candle crypto market scans for AI agents, with market states, reason codes, freshness and SNAP proof pointers where available. Paid in USDC on Base.