List the entity-matching scoring algorithms the /match endpoint accepts, each with the scoring features it uses, what each feature measures, its coefficient and a link to the imple

List the entity-matching scoring algorithms the /match endpoint accepts, each with the scoring features it uses, what each feature measures, its coefficient and a link to the implementation. Returns the six available algorithms (logic-v2, ofac, name-based, name-qualified, logic-v1, regression-v1), the one currently aliased as "best", and which alias is the default. Read this before tuning a screening threshold or reasoning about why a match scored as it did, so the threshold sent matches the algorithm actually scoring it — the score distributions differ sharply between a name-only matcher and a qualified one.

price-ascending: candidates are ordered by the listed price of the operation, with no managed-first preference applied. Unlike /v1/apis, this surface does not rank Apiosk-settled listings above federated ones — a comparison that reorders on commercial grounds is not a comparison. Pass sort=managed_first for the catalog's ordering.

Compared: listed price, settlement rail and input compatibility. Not measured yet: latency, reliability, result quality, and provider terms such as rate limits, jurisdiction and licensing.