Pinecone explains how text match filters scope vector searches for agents needing specific candidate pools.

{
  "signal_id": "215d4e47-20ba-4e2a-b448-8675584a836c",
  "signal_type": "linkedin-post-company",
  "signal_subtype": "linkedinPost",
  "detected_at": "2026-08-13T11:32:07.53+00:00",
  "company": {
    "name": "Pinecone",
    "domain": "pinecone.io"
  },
  "data": {
    "tags": [
      "Data Management",
      "Artificial Intelligence",
      "Information Technology"
    ],
    "summary": "Pinecone explains how text match filters scope vector searches for agents needing specific candidate pools.",
    "post_url": "https://www.linkedin.com/posts/pinecone-io_text-match-filters-for-agents-pinecone-activity-7493290270927523840-EDHC",
    "num_likes": 10,
    "post_text": "Most semantic search queries leave something unstated. The user knows what they mean. The system doesn't.\n\nPinecone's text match filters scope a vector search to a lexical condition (a machine number, a jurisdiction, a country) before the search runs, so an agent gets the right candidate pool without a dataset pre-labeled for every filter it might eventually need.\n\nHow it works, with a real example: https://lnkd.in/gZSrqApf",
    "posted_date": "2026-08-12T13:00:19.190Z",
    "num_comments": 1,
    "technologies_mentioned": [
      {
        "name": "Pinecone",
        "status": "using"
      }
    ]
  }
}

curl https://signals.autobound.ai/v1/signals/215d4e47-20ba-4e2a-b448-8675584a836c \
  -H "X-API-KEY: $AUTOBOUND_API_KEY"

curl -X POST https://signals.autobound.ai/v1/companies/enrich \
  -H "X-API-KEY: $AUTOBOUND_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"domain":"pinecone.io","limit":20}'