Fundable Location Taxonomy Lookup API

Use the Fundable Location Taxonomy Lookup API to search locations by name and optionally filter by type. Send a location name and optional city, state, region, or country type to the original Fundable REST endpoint using the documented request contract. Use it for geographic resolution, accurate filtering, and sourcing workflow preparation, connecting the returned records to the rest of your research or enrichment workflow. Review the detail page for supported parameters, request and response examples, identifier formats, and the configured per-request price. Examples describe the documented interface and should be checked against your own authorized upstream account before production use.

Selected price
$0.001 / callPublished pricing
Sellers / implementations
1 / 1
Requests · 30d
—Loading...
Success rate · 30d
—Loading...

Run sends a real API request. Charges follow the published API contract.

Request parameters
Location name to search for
Filter by specific location type
Alias for 'type' parameter

Sample response

{
  "data": {
    "locations": [
      {
        "location_type": "CITY",
        "name": "San Francisco",
        "permalink": "san-francisco-california"
      },
      {
        "location_type": "REGION",
        "name": "San Francisco Bay Area",
        "permalink": "san-francisco-bay-area"
      },
      {
        "location_type": "STATE",
        "name": "California",
        "permalink": "california"
      }
    ]
  },
  "meta": {
    "total_count": 3
  },
  "success": true
}

Response result

Response structure

Inferred from examples
  • dataobject
    • locationsobject[]
      • location_typestring
      • namestring
      • permalinkstring
  • metaobject
    • total_countinteger
  • successboolean

Common questions

Do I need a separate key for every provider?

Use your OpenAny API key for standard API access. Read it from OPENANY_API_KEY in your environment and keep it out of prompts, source code and logs.

Are these providers interchangeable?

No. Each offering has its own inputs, pricing and response contract. Selecting a catalog offering does not establish automatic routing or fallback. Confirm the service contract before calling.

How is this API billed?

API-key calls use your shared balance at the selected implementation's published rate. Check the billing unit and request-specific pricing rules before making a paid call. Recorded usage determines the final charge under that contract.

Where do the price and contract come from?

The selected implementation publishes its provider, request contract, revision and billing rules through OpenAny's public API catalog. A revision number identifies a contract version, not a price update date. A price update timestamp is not supplied; do not treat a page date as one.

How do OpenAny Balance and x402 differ?

OpenAny Balance uses an API key and one shared balance. Card, USDC and x402 top-ups, card auto top-up and USDC subscriptions fund that balance; available routes appear on the Credits page. Direct x402 is a separate pay-per-request flow, available only on listings that show it and requiring an authorized payment client.

Does Playground send a paid request?

Yes. After you sign in, Run sends a real API request using an active OpenAny API key. Charges follow the published API contract and use your shared balance. Selecting an implementation, editing inputs and viewing sample responses do not send requests.

Use Fundable Location Taxonomy Lookup API with your agent

Inspect endpoint contracts and confirm availability and pricing before a paid call.