HERGERT SYNTHORA
Integrate Synthora intelligence
Discover the resource. Check its conditions. Verify the result.
The public API offering uses x402 with USDC on Base. This guide distinguishes public discovery, the payment challenge and the delivered response. No account is needed to check the conditions.
Reading index
1. Discovery
Explore services · JSON catalog · Agent card
2. Payment challenge query
curl -i https://notary.hergertsynthora.com/service
The response to this query is HTTP 402 and includes x402Version, resource y accepts. A 402 describes the terms; it does not attest that payment was made or that the result was delivered.
In Notary, the published schema describes a POST request with JSON. Example body to query the operation contract; executing it requires following the payment or proof conditions announced by the service:
curl -i -X POST https://notary.hergertsynthora.com/service \
-H 'Content-Type: application/json' \
--data '{"op":"notarize","hash":"0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef"}'
The x402 client must check the challenge’s network, asset, amount and destination, authorize the payment and resend the request according to the protocol. Do not send private keys or recovery phrases to the service. X-WALLET, when the resource accepts it, identifies a public address; it is not a private key and does not replace the payment requirements.
3. Identity and charging
Agent registry: ERC-8004 #84581 en Base . The published x402 network is eip155:8453; the asset is USDC.
Destination declared by the catalog in this snapshot:
0x6D9F318463168fF637b50E5b9a21392e97c7c167
The cards and the catalog describe the same destination in this version. This documentation does not modify the services’ addresses nor does it alone attest ownership. If a request’s conditions differ from those published, check the catalog update before authorizing it.
4. Signature verification
There are two distinct objects. The discovery card is signed with the key synthora-mesh-attest published in this site’s JWKS . Its payload is the card’s JSON without signatures, with sorted keys, compact separators and UTF-8.
The API publishes its procedure for results at /pubkey : apply the declared format to the signed field and verify its receipt’s signature with the kid that corresponds to it. Do not swap the card key with the result key.
Tarjeta: protected_base64url + "." + base64url(JSON canónico sin signatures) Resultado: objeto y canonicalización declarados en /pubkey Algoritmo: Ed25519; seleccionar la clave por kid
A signature validates the object’s integrity and authorship, not the factual accuracy, freshness or sufficiency of the information. Assess the resource’s source, date, coverage and scope.
The historical September samples sign the ASCII hexadecimal SHA256 of the document; the October technical sheet declares a signature of its UTF-8 bytes. Use the signed object indicated by each format.
Download Python example to verify the card
5. Public map and protected core
curl -s https://mundo.hergertsynthora.com/mapstate
The map exposes its public state and the details of its layers. The core’s internal endpoints are not part of this public guide and may require additional authentication. This site does not distribute internal keys.