78trust / 100

German Company Data

by api.strale.io in Company & people data

x402 APIPassing, checked 2 h ago

Look up German Handelsregister company data via OpenRegister. Returns name, registration number, court, legal form, status, address, directors, capital, LEI, incorporation and termination dates.

GET https://api.strale.io/x402/german-company-data

Last 30 days

All checks passedSome failedAll failedNot checked

Status and outage history · Atom feed

Uptime
100%
Response time
284 ms typical, 364 ms slowest 5%
Last check
2 h ago
Next check
any minute now

How to call it

GET https://api.strale.io/x402/german-company-data

Each call costs $0.216 in USDC on Base, paid with the request over x402.

Run a free test callOne unpaid request, the way an agent sends it. You see the payment challenge it gets back. Nothing is charged.

Example request

Built from the input schema. Replace the values with your own.

GET https://api.strale.io/x402/german-company-data?company_id=example&company_name=example&court=example&hrb_number=example

Parameters

ParameterTypeRequiredDescription
company_idstringNoOpenRegister canonical id, e.g. "DE-HRB-F1103-267645". Preferred when known — skips name resolution and consumes one fewer API call.
company_namestringNoCompany name for fuzzy search via /v1/autocomplete/company.
courtstringNoRegistergericht (German commercial court). Required when providing 'hrb_number'. Example: "Amtsgericht Landsberg a. Lech".
hrb_numberstringNoHandelsregister number (e.g. "HRB 2001"). When provided, 'court' is also required — HRB/HRA numbers are per-court and not globally unique.

Example response

The listing has no example response.

Call it from code

The curl command shows the payment challenge. The JavaScript and Python versions pay and call, and never pay more than $0.216.

curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i 'https://api.strale.io/x402/german-company-data?company_id=example&company_name=example&court=example&hrb_number=example'

# x402 v2 sends the challenge base64-encoded in the PAYMENT-REQUIRED header (v1 sends it in the body).
# To read the header:
curl -sS -g -o /dev/null -D - 'https://api.strale.io/x402/german-company-data?company_id=example&company_name=example&court=example&hrb_number=example' \
  | grep -i '^payment-required:' | cut -d' ' -f2 | tr -d '\r' | base64 --decode
JavaScript: pay and call
// npm i @x402/fetch @x402/evm viem
import { wrapFetchWithPayment, x402Client } from "@x402/fetch";
import { registerExactEvmScheme } from "@x402/evm/exact/client";
import { privateKeyToAccount } from "viem/accounts";

// Pays at most $0.216 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.216" });
registerExactEvmScheme(client, { signer: privateKeyToAccount(process.env.EVM_PRIVATE_KEY) });
const pay = wrapFetchWithPayment(fetch, client);

// Not sure it's safe to pay? ToolVet checks it first for $0.005. Pay for that from a separate
// client: this one is capped at $0.216 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fapi.strale.io%2Fx402%2Fgerman-company-data
const res = await pay("https://api.strale.io/x402/german-company-data?company_id=example&company_name=example&court=example&hrb_number=example");
console.log(res.status, await res.text());
Python: pay and call
# pip install "x402[requests,evm]"
import os
from eth_account import Account
from x402 import x402ClientSync
from x402.http.clients import x402_requests
from x402.mechanisms.evm import EthAccountSigner
from x402.mechanisms.evm.exact.register import register_exact_evm_client

# Pays at most $0.216 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.216"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))

with x402_requests(client) as session:
    res = session.get("https://api.strale.io/x402/german-company-data?company_id=example&company_name=example&court=example&hrb_number=example")
    print(res.status_code, res.text)

Security scan

  • No findings. We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.

Recent checks

WhenResultHTTPTimePrice
2 h agoPassed402313 ms$0.216
6 h agoPassed402284 ms$0.216
10 h agoPassed402286 ms$0.216
14 h agoPassed402283 ms$0.216
18 h agoPassed402272 ms$0.216
22 h agoPassed402275 ms$0.216
26 h agoPassed402532 ms$0.216
29 h agoPassed402121 ms$0.216
33 h agoPassed402283 ms$0.216
36 h agoPassed402292 ms$0.216
40 h agoPassed402343 ms$0.216
44 h agoPassed402126 ms$0.216
47 h agoPassed402286 ms$0.216
2 days agoPassed402364 ms$0.216
2 days agoPassed402291 ms$0.216