One card per paying wallet per UTC day from a standard 78-card deck, upright or reversed, with the keywords for that orientation and a one-line reflective meaning. The deck is fixed and ships with th…
General Utilities x402 offerings
Browse indexable general utilities x402 offerings, including provider, method, and service details.
4051 indexable offerings in this category.
Offerings
Page 99 of 169A short, oblique fortune for the wallet that paid — drawn from the day's pool, stable for the whole UTC day, a different one tomorrow. You may send {"question": "…"} of up to 140 characters: it is ec…
A fortune cookie for the wallet that paid: one line drawn from the day's pool and keyed to the paying address, the same until midnight UTC and a new one after, plus six numbers between 1 and 99 drawn…
Percentage helper. op: "of" (a% of b), "change" (% change a→b), "ratio" (a is what % of b).
Neutral I-Ching bodygraph: the gate and line activations for the personality (birth) and design (Sun 88 degrees of arc before birth) sets, with the derived defined centers, channels, profile and a structural energy-type. Give a birth date, and for full accuracy a time, place and tz or utc_offset. Computed, not interpreted.
Neutral I-Ching bodygraph: the gate and line activations for the personality (birth) and design (Sun 88 degrees of arc before birth) sets, with the derived defined centers, channels, profile and a structural energy-type. Give a birth date, and for full accuracy a time, place and tz or utc_offset. Computed, not interpreted.
Multi-framework birth-chart in ONE call: western natal astrology, Vedic sidereal positions, Chinese BaZi, Pythagorean numerology, a neutral I-Ching bodygraph and biorhythms. Give a birth date (optional time, place or lat and lon, and tz or utc_offset) and get cited JSON across every system. Deterministic, no LLM, no keys.
Prüft am Objekt alternate den Befund Länge des Ankertexts.
Prüft am Objekt alternate den Befund Länge des Ankertexts.
Phishing domain check: domain age, registrar, DNS, TLS certificate and brand lookalikes. Is this link safe to send a user to? Pass ?domain= (or a URL). From public records: when it was registered and by which registrar (RDAP, the registry's own record), its DNS, who issued its TLS certificate and until when, and whether the name imitates one of 40 brands phishing kits copy (coinbase, metamask, uniswap...). A record we could not read is reported as unread, never as clean. Paid in USDC on Base.
Parse and validate any phone number in any format, identify its country and line type (mobile/landline/VOIP/toll-free/premium for NANP + UK numbers; other countries return line_type unknown), and return all standard format variants (E.164, international, national) — catches fictional/unassigned NANP numbers (555 area code, 555-01XX range) so agents can validate contacts and normalize phone data without a paid telecom API.
Use when an agent must decide whether a phone number is usable before writing or calling: checks it offline, normalises it to E.164, works out its country (including the twelve calling codes shared by several countries) and validates the national length against that country's numbering plan, returning the tel: URI and the national dialling form. Data from Google's libphonenumber, no network call, so it cannot fail because a third party is down.
Parse and validate any phone number worldwide using libphonenumber. Returns is_valid, e164 (canonical international format e.g. '+4917612345678'), national_format, country_code (ISO alpha-2), and line_type (MOBILE/FIXED_LINE/VOIP/TOLL_FREE). Provide country_code hint (e.g. 'DE') for local numbers without country prefix.
Validate and normalize a phone number from any country: E.164, national and international format, type (mobile, landline, toll-free, VoIP...), country, region, original carrier and time zones. Nothing is called or stored.
Phone Numbers to E.164 — Turns a list of phone numbers written any way people write them into E.164 (a plus sign, the country code and the national number, digits only), one JSON object per number, using a default country the request states. Where plain models slip - the trunk 0 left in, "+44 (0)20" glued to a stray zero, Italian numbers with the leading 0 wrongly dropped, the leading 1 of a North American number kept, a made-up country for a bare local number, an extension stuck onto the numbe…
Before your agent stores or messages a phone number: validate and normalize it offline — E.164 formatting, region, national format and line type from Google's libphonenumber metadata, no network call
Validate and parse phone numbers in international E.164 form: extract the country calling code and region, the national number, and the canonical +E.164 string. Single number or a batch of up to 50. Format validation, not a line-in-service check. POST a JSON body like: {"phone":"+14155552671"}
Parse, validate and format a phone number — E.164/national/international/RFC 3966, region and line type (syntactic validation, no carrier lookup).
Returns a scored, ranked list of x402 API endpoints that best match the intent — with price, latency, input schema, and description. Flat $0.01 USDC per query.
Extended descriptive history within the retention window.
Uncensored one-turn chat (abliterated LLM): direct, specific answers to any prompt.
Analyzes and scores proposed plans, identifies weaknesses, and generates targeted adjustments to optimize outcomes.
Whether to open a specific Texas Hold'em starting hand from a named position against a given number of opponents, with the engine equity behind the answer.
The full record for one of the 1,326 specific Texas Hold'em starting hands: equity against modelled ranges, position-by-position opening guidance, exact head-to-head figures, and the exact card-removal effect of holding these specific two cards.
