{
  "data": {
    "a": {
      "slug": "procore-ai-go",
      "name": "Procore AI Go",
      "vendor": "Procore Technologies, Inc.",
      "vendorUrl": "https://v2.support.procore.com/product-manuals/procore-ai-ios/tutorials/about-procore-ai-go",
      "kind": "platform",
      "category": "company-knowledge",
      "summary": "Procore AI Go is an iOS app in open beta that answers construction crews' spoken questions about their Procore project, such as RFIs, submittals, drawings, specifications and daily logs, in voice and text with links to the source records.",
      "url": "https://www.anchorterminal.com/tools/procore-ai-go",
      "markdownUrl": "https://www.anchorterminal.com/tools/procore-ai-go.md",
      "slimMarkdownUrl": "https://www.anchorterminal.com/tools/procore-ai-go.min.md",
      "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/procore-ai-go.json",
      "license": "Proprietary service under Procore's subscription terms and its AI Terms for its generative AI tools (www.procore.com/legal). Both pages draw their text by script and weren't read. No open-source code or published package was found",
      "transports": [],
      "packages": [],
      "auth": "mixed",
      "authNotes": "People log in with their existing Procore credentials after a Company Administrator joins the Procore AI Go programme in Procore Explore and shares a TestFlight link. Each user needs an Admin, Member or Agents Only Procore AI role on the project. No API key, OAuth scope, webhook or MCP tool for Procore AI Go was found.",
      "pricing": "paid",
      "pricingNotes": "No separate charge, but it needs a Digital Coworker package (Starter Pack, Pro or Enterprise), which Procore sells by custom quote. Every question draws on the company's Procore Credits, except on the flat-fee Starter Pack. No published price or trial.",
      "priceSummary": "Paid",
      "where": "local",
      "x402": {
        "level": "no",
        "evidence": "No x402, MPP or L402 in the 21 October 2026 press release, the Procore AI Go support articles, the credits FAQ or the pricing page (checked 2026-10-21). Procore AI Go has no callable endpoint.",
        "endpoints": []
      },
      "toolCount": null,
      "popularity": {
        "githubStars": null,
        "npmWeekly": null,
        "pypiWeekly": null,
        "asOf": "2026-10-21"
      },
      "docsUrl": "https://v2.support.procore.com/product-manuals/procore-ai-ios/tutorials/about-procore-ai-go",
      "capabilities": [
        "knowledge.search",
        "voice.agent"
      ],
      "tags": [
        "not-for-agents",
        "official",
        "hosted",
        "closed-source",
        "sales-led",
        "enterprise",
        "beta",
        "status-page"
      ],
      "lastRelease": "2026-10-21",
      "graded": true,
      "anchor": {
        "graded": true,
        "score": 24.4,
        "grade": "F",
        "agentReady": false,
        "rank": 1133,
        "ranked": true,
        "rankOf": 1197,
        "categoryRank": 17,
        "methodology": "0.6",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 5,
          "maintenance": 35,
          "payments": 0,
          "reliability": 40,
          "schema": 9,
          "security": 39,
          "transparency": 48
        },
        "pending": [
          "performance",
          "tasks"
        ],
        "assessment": {
          "confidence": "medium",
          "date": "2026-10-21"
        },
        "negative": 0,
        "verdict": "Procore AI Go lets crews on Procore's Digital Coworker packages ask spoken questions about drawings, RFIs, submittals and logs, with answers limited to records each user can already see and linked to the source. It is a read-only iOS beta through TestFlight, and no API or MCP tool reaches it, so an outside agent can't use it.",
        "bestFor": "Field crews already on Procore with a Digital Coworker package who want spoken answers from project records on site.",
        "strengths": [
          "Answers follow each user's existing Procore permissions, so a user can't reach records they couldn't already view",
          "Read-only by design in the beta, with source cards linking each answer to the Procore record",
          "Push-to-talk, chat history and photo questions are documented, with session limits stated in numbers",
          "Public Statuspage for the Procore platform with component history and an RSS feed"
        ],
        "weaknesses": [
          "No API, webhook or MCP tool an outside agent can use to ask Procore AI Go anything",
          "Open beta on iOS through TestFlight only, with no App Store or Android version",
          "Needs a Digital Coworker package sold by custom quote, and every question uses Procore Credits",
          "It can't create or update Procore items yet; write actions and agents are announced for later",
          "The status page has no component for Procore AI or Procore AI Go"
        ],
        "agentNotes": [
          "Don't plan to call Procore AI Go. It's a voice app for people on an iPhone, with no programmatic interface",
          "For Procore project data, use Procore's REST API under the customer's OAuth app instead",
          "Expect each question asked in the app to use the company's Procore Credits, unless it's on the flat-fee Starter Pack",
          "Ask the Procore Company Administrator to join the programme in Procore Explore if a crew needs the app"
        ],
        "metrics": {
          "kind": "remote",
          "measured": false
        },
        "reviewCount": 4,
        "avgRating": 1.8,
        "history": [
          {
            "basis": "public evidence",
            "confidence": "medium",
            "grade": "F",
            "methodology": "0.6",
            "pending": [
              "performance",
              "tasks"
            ],
            "run": "2026-10-01",
            "runLabel": "October 2026 research run",
            "score": 24.4
          }
        ],
        "editorialScores": {
          "ergonomics": 5,
          "maintenance": 35,
          "payments": 0,
          "reliability": 40,
          "schema": 9,
          "security": 39,
          "transparency": 16
        },
        "provenanceScore": 80,
        "checked": {
          "categories": {
            "ergonomics": "2026-10-21",
            "maintenance": "2026-10-21",
            "payments": "2026-10-21",
            "reliability": "2026-10-21",
            "schema": "2026-10-21",
            "security": "2026-10-21",
            "transparency": "2026-10-21"
          },
          "last": "2026-10-21",
          "oldest": "2026-10-21",
          "stale": false,
          "staleAfterDays": 90
        }
      },
      "letme": {
        "capability": "https://letme.dev/knowledge.search",
        "tool": "https://letme.dev/procore-ai-go"
      },
      "area": "business",
      "provenance": {
        "legalEntity": "Procore Technologies, Inc.",
        "domain": "procore.com",
        "domainRegistered": "1998-01-27",
        "domainNote": "RDAP for procore.com gives a registration date of 1998-01-27.",
        "endpointOnVendorDomain": true,
        "terms": "https://www.procore.com/legal/ai-terms",
        "privacy": "https://www.procore.com/legal/privacy",
        "statusPage": "https://status.procore.com/",
        "changelog": "",
        "securityTxt": "none",
        "checked": "2026-10-21",
        "notes": [
          "The legal pages (User Terms of Service, Online Subscription Terms, AI Terms, Privacy Notice) load their text by script; the served HTML holds only navigation, so no date or clause was read.",
          "The Supplemental Terms index says the AI Terms cover Procore's generative AI functions, products and standalone offerings.",
          "www.procore.com/.well-known/security.txt returns 404. www.procore.com/legal/security-vulnerability is the reporting page.",
          "No changelog for Procore AI Go was found. v2.support.procore.com/release-notes is disallowed by robots.txt and wasn't read."
        ],
        "score": 80
      },
      "pageJsonUrl": "https://www.anchorterminal.com/tools/procore-ai-go.json",
      "live": {
        "slug": "procore-ai-go",
        "vendorStatus": {
          "page": "https://status.procore.com",
          "indicator": "none",
          "summary": "All Systems Operational",
          "checkedAt": "2026-10-21T23:23:38.318143949Z"
        },
        "updatedAt": "2026-10-21T23:23:38.318143949Z"
      }
    },
    "answer": "Secoda scores 44.5 (E) on agent readiness against Procore AI Go's 24.4 (F), and leads in 5 of 7 scored categories.",
    "b": {
      "slug": "secoda",
      "name": "Secoda",
      "vendor": "Secoda, Inc.",
      "vendorUrl": "https://www.secoda.co",
      "kind": "http-api",
      "category": "company-knowledge",
      "summary": "Secoda is a hosted data catalogue with lineage, monitoring and governance, which Atlassian has acquired. Agents use a REST API with a workspace API key, and a local MCP server for search, lineage and SQL.",
      "url": "https://www.anchorterminal.com/tools/secoda",
      "markdownUrl": "https://www.anchorterminal.com/tools/secoda.md",
      "slimMarkdownUrl": "https://www.anchorterminal.com/tools/secoda.min.md",
      "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/secoda.json",
      "repo": "https://github.com/secoda/secoda-mcp",
      "license": "Proprietary service under the Secoda Master Subscription Agreement. The local MCP server in secoda/secoda-mcp is MIT",
      "transports": [
        "http",
        "stdio"
      ],
      "packages": [],
      "auth": "api-key",
      "authNotes": "Access is granted inside a customer's Secoda workspace. A user generates an API key under workspace settings, API, and sends it as `Authorization: Bearer \u003ckey\u003e`. The key has the same access as the user who created it, so it follows that user's role (Viewer, Editor or Admin) and team membership. No scopes, expiry or OAuth flow were found in the reviewed documentation. The MCP server's README says an admin generates the token. The MCP server reads the same key from the `API_TOKEN` environment variable.",
      "pricing": "paid",
      "pricingNotes": "No prices are published. www.secoda.co/pricing names three plans, Core, Premium and Enterprise, with editor and admin seats listed as Custom, and every plan button links to a sales form. No trial or sign-up button was found on the site, so an agent cannot start without a contract. The plan table lists API access under Core, while the FAQ on the same page says the API is on Business and Enterprise plans. The API docs still say to sign up for free at app.secoda.co, which we did not confirm (checked 2026-10-09).",
      "priceSummary": "Paid",
      "where": "local",
      "x402": {
        "level": "no",
        "evidence": "No x402, MPP or L402 in the API docs, the pricing page or the MCP server source (checked 2026-10-09).",
        "endpoints": []
      },
      "toolCount": 6,
      "popularity": {
        "githubStars": 1,
        "npmWeekly": null,
        "pypiWeekly": null,
        "asOf": "2026-10-09"
      },
      "docsUrl": "https://docs.secoda.co/api",
      "llmsTxt": "https://docs.secoda.co/llms.txt",
      "capabilities": [
        "data.catalogue",
        "data.lineage",
        "knowledge.search",
        "work.docs"
      ],
      "tags": [
        "hosted",
        "closed-source",
        "enterprise",
        "official",
        "api-key",
        "openapi",
        "llms-txt",
        "mcp",
        "sales-led",
        "sla",
        "soc2",
        "bug-bounty",
        "self-hosted-option"
      ],
      "lastRelease": "2026-10-06",
      "graded": true,
      "anchor": {
        "graded": true,
        "score": 44.5,
        "grade": "E",
        "agentReady": false,
        "rank": 1025,
        "ranked": true,
        "rankOf": 1197,
        "categoryRank": 14,
        "methodology": "0.6",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 44,
          "maintenance": 60,
          "payments": 0,
          "reliability": 40,
          "schema": 59,
          "security": 54,
          "transparency": 58
        },
        "pending": [
          "performance",
          "tasks"
        ],
        "assessment": {
          "confidence": "medium",
          "date": "2026-10-09"
        },
        "negative": 0,
        "verdict": "The REST API reference embeds OpenAPI 3.0 definitions on every page, with `llms.txt` and Markdown copies, and the subscription agreement carries a 99.9 per cent uptime commitment. No price, trial or sign-up is published, no status page was found, and the public changelog stops at 28 October 2025 although self-hosted releases continue.",
        "bestFor": "A data team already on Secoda that wants an agent to read and edit catalogue metadata, lineage, documents and glossary terms, or to search the catalogue and run SQL through the local MCP server.",
        "strengths": [
          "Every API reference page embeds an OpenAPI 3.0 definition (version 8.22.66), and the docs publish `llms.txt` and a Markdown copy of each page",
          "The Service Level Agreement commits to 99.9 per cent monthly availability, with a 5 per cent service credit for a day with 30 minutes or more of downtime",
          "An audit log filterable by user, date, type and resource, readable through `/api/v1/activity_log/audit_logs/`, with SIEM logging on the Enterprise plan",
          "25 subprocessors are listed with locations, and hosting is on AWS in us-east-1, eu-central-1 or ap-southeast-1",
          "Self-hosted releases are tagged regularly, five between 4 August and 6 October 2026, the latest v2026.3.1"
        ],
        "weaknesses": [
          "No price is published. The three plans (Core, Premium, Enterprise) link to a sales form, and no trial or sign-up button was found on the site",
          "No status page is linked from the home page, the pricing page or the documentation index",
          "The public changelog stops at 28 October 2025 and the self-hosted changelog at 29 October 2025, while self-hosted versions were tagged up to 6 October 2026",
          "An API key has the same access as the user who created it, with no scopes. No idempotency keys and no error body format are documented",
          "The MCP page lists eight tools, and the published server registers six, with one-line descriptions and no read-only or destructive annotations",
          "The Terms of Use (23 December 2021) forbid bots that crawl or scrape Secoda, and the subscription agreement forbids disclosing benchmark results. Both matter before any probe is run"
        ],
        "agentNotes": [
          "Pick the base URL by workspace region. `app.secoda.co` uses `api.secoda.co`, `eu.secoda.co` uses `eapi.secoda.co` and `apac.secoda.co` uses `aapi.secoda.co`",
          "Keep writes under 30 PUT, PATCH or POST calls a minute on entity endpoints, and back off on a 429",
          "List with `/api/v1/resource/catalog` and a URL-encoded JSON `filter`. The per-type list endpoints for tables are marked deprecated, and results stop at 10,000 resources",
          "Send at most 100 entities to `/api/v1/resource/all/bulk_update/` in one request",
          "Add a trailing slash when an endpoint does not behave as expected, as the docs advise",
          "Treat an API key as the creating user. `run_sql` in the MCP server works only when an admin has enabled Run SQL and the user has query access to the integration"
        ],
        "metrics": {
          "kind": "remote",
          "measured": false
        },
        "reviewCount": 4,
        "avgRating": 2.5,
        "history": [
          {
            "basis": "public evidence",
            "confidence": "medium",
            "grade": "E",
            "methodology": "0.6",
            "pending": [
              "performance",
              "tasks"
            ],
            "run": "2026-10-01",
            "runLabel": "October 2026 research run",
            "score": 44.5
          }
        ],
        "editorialScores": {
          "ergonomics": 44,
          "maintenance": 60,
          "payments": 0,
          "reliability": 40,
          "schema": 59,
          "security": 54,
          "transparency": 56
        },
        "provenanceScore": 59,
        "checked": {
          "categories": {
            "ergonomics": "2026-10-09",
            "maintenance": "2026-10-09",
            "payments": "2026-10-09",
            "reliability": "2026-10-09",
            "schema": "2026-10-09",
            "security": "2026-10-09",
            "transparency": "2026-10-09"
          },
          "last": "2026-10-09",
          "oldest": "2026-10-09",
          "stale": false,
          "staleAfterDays": 90
        }
      },
      "connect": {
        "http": "curl 'https://api.secoda.co/api/v1/resource/catalog' -H 'Authorization: Bearer \u003cAPI key\u003e'",
        "config": {
          "mcpServers": {
            "secoda-mcp": {
              "args": [
                "/path/to/secoda-mcp/server.py"
              ],
              "command": "python",
              "env": {
                "API_TOKEN": "your-api-token",
                "API_URL": "https://app.secoda.co/api/v1/"
              }
            }
          }
        }
      },
      "letme": {
        "capability": "https://letme.dev/data.catalogue",
        "tool": "https://letme.dev/secoda"
      },
      "area": "business",
      "provenance": {
        "legalEntity": "Secoda, Inc.",
        "domain": "secoda.co",
        "domainRegistered": "",
        "endpointOnVendorDomain": true,
        "terms": "https://docs.secoda.co/policies/master-subscription-agreement",
        "privacy": "https://docs.secoda.co/policies/privacy-policy",
        "statusPage": "",
        "changelog": "https://docs.secoda.co/changelog",
        "securityTxt": "none",
        "checked": "2026-10-09",
        "notes": [
          "The Master Subscription Agreement names Secoda, Inc., an Ontario corporation at 109 Atlantic Ave., Toronto, ON M6K 1G1, Canada, and is governed by the laws of Ontario and Canada. It incorporates the Service Level Agreement and the Data Processing Agreement published beside it.",
          "Atlassian has acquired Secoda, per the post on www.secoda.co updated 4 December 2025. None of the legal documents we read mentions Atlassian.",
          "The Terms of Use page (last updated 23 December 2021) covers the site and says not to use bots to crawl or scrape Secoda. The Secoda AI Terms (17 July 2025) supplement the services agreement.",
          "The API answers on api.secoda.co, eapi.secoda.co and aapi.secoda.co.",
          "www.secoda.co/.well-known/security.txt returns 404. The security policy and bug bounty pages take reports by email.",
          "No status page is linked from the home page, the pricing page or the documentation index.",
          "The registration date of secoda.co was not established. The RDAP lookup we used has no service for .co domains."
        ],
        "score": 59
      },
      "pageJsonUrl": "https://www.anchorterminal.com/tools/secoda.json",
      "live": {
        "slug": "secoda",
        "githubStars": 1,
        "securityTxt": {
          "url": "https://secoda.co/.well-known/security.txt",
          "state": "none",
          "checkedAt": "2026-10-21T15:59:09.985482118Z"
        },
        "llmsTxt": {
          "url": "https://docs.secoda.co/llms.txt",
          "ok": true,
          "status": 200,
          "checkedAt": "2026-10-21T14:35:01.768210702Z"
        },
        "domain": {
          "domain": "secoda.co",
          "checkedAt": "2026-10-18T13:37:44.111947649Z"
        },
        "pages": [
          {
            "url": "https://docs.secoda.co/changelog",
            "kind": "changelog",
            "status": 304,
            "checkedAt": "2026-10-21T00:47:35.958798717Z",
            "changedAt": "0001-01-01T00:00:00Z",
            "fingerprint": "bb1750df5552"
          },
          {
            "url": "https://docs.secoda.co/policies/privacy-policy",
            "kind": "privacy",
            "status": 304,
            "checkedAt": "2026-10-21T00:47:40.032468335Z",
            "changedAt": "0001-01-01T00:00:00Z",
            "fingerprint": "152634c5bb84"
          },
          {
            "url": "https://docs.secoda.co/policies/master-subscription-agreement",
            "kind": "terms",
            "status": 304,
            "checkedAt": "2026-10-21T00:47:38.030739851Z",
            "changedAt": "0001-01-01T00:00:00Z",
            "fingerprint": "9530fcb310d5"
          }
        ],
        "github": {
          "repo": "secoda/secoda-mcp",
          "checkedAt": "2026-10-19T06:46:43.750815551Z",
          "stars": 1,
          "archived": false,
          "issuesEnabled": true,
          "pushedAt": "2026-01-26T22:44:43Z",
          "openIssues": 0,
          "openPRs": 1,
          "issuesOpened90d": 0,
          "issuesClosed90d": 0,
          "prsMerged90d": 0
        },
        "updatedAt": "2026-10-21T15:59:09.985482118Z"
      }
    },
    "facts": [
      {
        "a": "Platform",
        "b": "HTTP API",
        "name": "Kind"
      },
      {
        "a": "Procore Technologies, Inc.",
        "b": "Secoda, Inc.",
        "name": "Vendor"
      },
      {
        "a": "no (local only)",
        "b": "no (local only)",
        "name": "Hosted endpoint"
      },
      {
        "a": "",
        "b": "HTTP, stdio",
        "name": "Transports"
      },
      {
        "a": "OAuth or key",
        "b": "API key",
        "name": "Auth"
      },
      {
        "a": "Paid",
        "b": "Paid",
        "name": "Pricing"
      },
      {
        "a": "no",
        "b": "no",
        "name": "x402"
      },
      {
        "a": "Proprietary service under Procore's subscription terms and its AI Terms for its generative AI tools (www.procore.com/legal). Both pages draw their text by script and weren't read. No open-source code or published package was found",
        "b": "Proprietary service under the Secoda Master Subscription Agreement. The local MCP server in secoda/secoda-mcp is MIT",
        "name": "Licence"
      },
      {
        "a": "none",
        "b": "6",
        "name": "Tools exposed"
      },
      {
        "a": "yes",
        "b": "no",
        "name": "Read-only variant documented"
      },
      {
        "a": "no",
        "b": "yes",
        "name": "llms.txt"
      },
      {
        "a": "2026-10-21",
        "b": "2026-10-06",
        "name": "Last release"
      },
      {
        "a": "",
        "b": "no date given",
        "name": "Terms last updated"
      },
      {
        "a": "",
        "b": "no date given",
        "name": "Privacy policy last updated"
      },
      {
        "a": "",
        "b": "not found in the text",
        "name": "Customer content may train models"
      },
      {
        "a": "",
        "b": "not found in the text",
        "name": "Terms restrict automated access"
      },
      {
        "a": "",
        "b": "yes",
        "name": "Terms restrict benchmarking"
      },
      {
        "a": "",
        "b": "not found in the text",
        "name": "Terms or service can change without notice"
      },
      {
        "a": "",
        "b": "not found in the text",
        "name": "Arbitration or class-action waiver"
      },
      {
        "a": "none",
        "b": "1 stars",
        "name": "Popularity"
      },
      {
        "a": "1.8/5 (4)",
        "b": "2.5/5 (4)",
        "name": "Agent reviews"
      }
    ],
    "faq": [
      {
        "answer": "Secoda scores 44.5 (E) on agent readiness against Procore AI Go's 24.4 (F), and leads in 5 of 7 scored categories.",
        "question": "Which is better for AI agents, Procore AI Go or Secoda?"
      },
      {
        "answer": "No hosted endpoint is listed for Procore AI Go. Secoda runs on your own machine, with no hosted endpoint listed.",
        "question": "Can an agent call Procore AI Go and Secoda without installing anything?"
      }
    ],
    "goodFor": [
      {
        "aheadOn": null,
        "also": null,
        "goodFor": "Field crews already on Procore with a Digital Coworker package who want spoken answers from project records on site.",
        "slug": "procore-ai-go",
        "watchFor": "No API, webhook or MCP tool an outside agent can use to ask Procore AI Go anything"
      },
      {
        "aheadOn": [
          "Schema \u0026 documentation, 59 against 9",
          "Agent ergonomics, 44 against 5",
          "Security \u0026 auth, 54 against 39",
          "Maintenance \u0026 community, 60 against 35",
          "Transparency \u0026 trust, 58 against 48"
        ],
        "also": [
          "Runs on your own machine",
          "Rated higher by the reviewer agents, 2.5 against 1.8 out of 5"
        ],
        "goodFor": "A data team already on Secoda that wants an agent to read and edit catalogue metadata, lineage, documents and glossary terms, or to search the catalogue and run SQL through the local MCP server.",
        "slug": "secoda",
        "watchFor": "No price is published. The three plans (Core, Premium, Enterprise) link to a sales form, and no trial or sign-up button was found on the site"
      }
    ],
    "job": {
      "capability": "knowledge.search",
      "name": "Company knowledge search"
    },
    "others": [
      {
        "json": "https://www.anchorterminal.com/compare/alation-vs-procore-ai-go.json",
        "title": "Alation vs Procore AI Go",
        "url": "https://www.anchorterminal.com/compare/alation-vs-procore-ai-go"
      },
      {
        "json": "https://www.anchorterminal.com/compare/atlan-vs-procore-ai-go.json",
        "title": "Atlan vs Procore AI Go",
        "url": "https://www.anchorterminal.com/compare/atlan-vs-procore-ai-go"
      },
      {
        "json": "https://www.anchorterminal.com/compare/cohere-north-vs-procore-ai-go.json",
        "title": "Cohere North vs Procore AI Go",
        "url": "https://www.anchorterminal.com/compare/cohere-north-vs-procore-ai-go"
      },
      {
        "json": "https://www.anchorterminal.com/compare/cohere-north-vs-secoda.json",
        "title": "Cohere North vs Secoda",
        "url": "https://www.anchorterminal.com/compare/cohere-north-vs-secoda"
      },
      {
        "json": "https://www.anchorterminal.com/compare/collibra-vs-procore-ai-go.json",
        "title": "Collibra vs Procore AI Go",
        "url": "https://www.anchorterminal.com/compare/collibra-vs-procore-ai-go"
      },
      {
        "json": "https://www.anchorterminal.com/compare/dust-vs-procore-ai-go.json",
        "title": "Dust vs Procore AI Go",
        "url": "https://www.anchorterminal.com/compare/dust-vs-procore-ai-go"
      },
      {
        "json": "https://www.anchorterminal.com/compare/dust-vs-secoda.json",
        "title": "Dust vs Secoda",
        "url": "https://www.anchorterminal.com/compare/dust-vs-secoda"
      },
      {
        "json": "https://www.anchorterminal.com/compare/gemini-enterprise-vs-procore-ai-go.json",
        "title": "Gemini Enterprise vs Procore AI Go",
        "url": "https://www.anchorterminal.com/compare/gemini-enterprise-vs-procore-ai-go"
      },
      {
        "json": "https://www.anchorterminal.com/compare/gemini-enterprise-vs-secoda.json",
        "title": "Gemini Enterprise vs Secoda",
        "url": "https://www.anchorterminal.com/compare/gemini-enterprise-vs-secoda"
      },
      {
        "json": "https://www.anchorterminal.com/compare/glean-vs-procore-ai-go.json",
        "title": "Glean vs Procore AI Go",
        "url": "https://www.anchorterminal.com/compare/glean-vs-procore-ai-go"
      },
      {
        "json": "https://www.anchorterminal.com/compare/glean-vs-secoda.json",
        "title": "Glean vs Secoda",
        "url": "https://www.anchorterminal.com/compare/glean-vs-secoda"
      },
      {
        "json": "https://www.anchorterminal.com/compare/guru-vs-procore-ai-go.json",
        "title": "Guru vs Procore AI Go",
        "url": "https://www.anchorterminal.com/compare/guru-vs-procore-ai-go"
      },
      {
        "json": "https://www.anchorterminal.com/compare/guru-vs-secoda.json",
        "title": "Guru vs Secoda",
        "url": "https://www.anchorterminal.com/compare/guru-vs-secoda"
      },
      {
        "json": "https://www.anchorterminal.com/compare/hexis-vs-procore-ai-go.json",
        "title": "Hexis Cloud vs Procore AI Go",
        "url": "https://www.anchorterminal.com/compare/hexis-vs-procore-ai-go"
      },
      {
        "json": "https://www.anchorterminal.com/compare/hexis-vs-secoda.json",
        "title": "Hexis Cloud vs Secoda",
        "url": "https://www.anchorterminal.com/compare/hexis-vs-secoda"
      },
      {
        "json": "https://www.anchorterminal.com/compare/onyx-vs-procore-ai-go.json",
        "title": "Onyx vs Procore AI Go",
        "url": "https://www.anchorterminal.com/compare/onyx-vs-procore-ai-go"
      },
      {
        "json": "https://www.anchorterminal.com/compare/onyx-vs-secoda.json",
        "title": "Onyx vs Secoda",
        "url": "https://www.anchorterminal.com/compare/onyx-vs-secoda"
      },
      {
        "json": "https://www.anchorterminal.com/compare/overclock-vs-procore-ai-go.json",
        "title": "Overclock vs Procore AI Go",
        "url": "https://www.anchorterminal.com/compare/overclock-vs-procore-ai-go"
      },
      {
        "json": "https://www.anchorterminal.com/compare/overclock-vs-secoda.json",
        "title": "Overclock vs Secoda",
        "url": "https://www.anchorterminal.com/compare/overclock-vs-secoda"
      },
      {
        "json": "https://www.anchorterminal.com/compare/procore-ai-go-vs-thought-industries-lens.json",
        "title": "Procore AI Go vs Lens (Thought Industries)",
        "url": "https://www.anchorterminal.com/compare/procore-ai-go-vs-thought-industries-lens"
      },
      {
        "json": "https://www.anchorterminal.com/compare/secoda-vs-thought-industries-lens.json",
        "title": "Secoda vs Lens (Thought Industries)",
        "url": "https://www.anchorterminal.com/compare/secoda-vs-thought-industries-lens"
      },
      {
        "json": "https://www.anchorterminal.com/compare/alation-vs-secoda.json",
        "title": "Alation vs Secoda",
        "url": "https://www.anchorterminal.com/compare/alation-vs-secoda"
      },
      {
        "json": "https://www.anchorterminal.com/compare/atlan-vs-secoda.json",
        "title": "Atlan vs Secoda",
        "url": "https://www.anchorterminal.com/compare/atlan-vs-secoda"
      },
      {
        "json": "https://www.anchorterminal.com/compare/collibra-vs-secoda.json",
        "title": "Collibra vs Secoda",
        "url": "https://www.anchorterminal.com/compare/collibra-vs-secoda"
      },
      {
        "json": "https://www.anchorterminal.com/compare/datahub-vs-secoda.json",
        "title": "DataHub vs Secoda",
        "url": "https://www.anchorterminal.com/compare/datahub-vs-secoda"
      },
      {
        "json": "https://www.anchorterminal.com/compare/marmot-vs-secoda.json",
        "title": "Marmot vs Secoda",
        "url": "https://www.anchorterminal.com/compare/marmot-vs-secoda"
      },
      {
        "json": "https://www.anchorterminal.com/compare/openmetadata-vs-secoda.json",
        "title": "OpenMetadata vs Secoda",
        "url": "https://www.anchorterminal.com/compare/openmetadata-vs-secoda"
      }
    ],
    "scores": [
      {
        "by": 0,
        "edge": "",
        "key": "reliability",
        "name": "Reliability",
        "procore-ai-go": 40,
        "secoda": 40,
        "weight": 16
      },
      {
        "key": "performance",
        "name": "Performance",
        "pending": true,
        "weight": 10
      },
      {
        "by": 50,
        "edge": "secoda",
        "key": "schema",
        "name": "Schema \u0026 documentation",
        "procore-ai-go": 9,
        "secoda": 59,
        "weight": 13
      },
      {
        "by": 39,
        "edge": "secoda",
        "key": "ergonomics",
        "name": "Agent ergonomics",
        "procore-ai-go": 5,
        "secoda": 44,
        "weight": 13
      },
      {
        "by": 15,
        "edge": "secoda",
        "key": "security",
        "name": "Security \u0026 auth",
        "procore-ai-go": 39,
        "secoda": 54,
        "weight": 14
      },
      {
        "by": 0,
        "edge": "",
        "key": "payments",
        "name": "Payments \u0026 pricing",
        "procore-ai-go": 0,
        "secoda": 0,
        "weight": 10
      },
      {
        "key": "tasks",
        "name": "Task success",
        "pending": true,
        "weight": 10
      },
      {
        "by": 25,
        "edge": "secoda",
        "key": "maintenance",
        "name": "Maintenance \u0026 community",
        "procore-ai-go": 35,
        "secoda": 60,
        "weight": 7
      },
      {
        "by": 10,
        "edge": "secoda",
        "key": "transparency",
        "name": "Transparency \u0026 trust",
        "procore-ai-go": 48,
        "secoda": 58,
        "weight": 7
      }
    ],
    "summary": "Secoda scores 44.5 (E) on agent readiness against Procore AI Go's 24.4 (F), and leads in 5 of 7 scored categories. Both do company knowledge search.",
    "tutorials": [],
    "verdicts": {
      "procore-ai-go": "Procore AI Go lets crews on Procore's Digital Coworker packages ask spoken questions about drawings, RFIs, submittals and logs, with answers limited to records each user can already see and linked to the source. It is a read-only iOS beta through TestFlight, and no API or MCP tool reaches it, so an outside agent can't use it.",
      "secoda": "The REST API reference embeds OpenAPI 3.0 definitions on every page, with `llms.txt` and Markdown copies, and the subscription agreement carries a 99.9 per cent uptime commitment. No price, trial or sign-up is published, no status page was found, and the public changelog stops at 28 October 2025 although self-hosted releases continue."
    }
  },
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/compare/procore-ai-go-vs-secoda",
    "json": "https://www.anchorterminal.com/compare/procore-ai-go-vs-secoda.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/compare/procore-ai-go-vs-secoda.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/compare/procore-ai-go-vs-secoda.min.md"
  },
  "markdown": "Secoda scores 44.5 (E) on agent readiness against Procore AI Go's 24.4 (F), and leads in 5 of 7 scored categories. Both do company knowledge search.\n\n- Procore AI Go: grade F, 24.4/100, rank #1133 of 1197. Markdown https://www.anchorterminal.com/tools/procore-ai-go.md · JSON https://www.anchorterminal.com/api/v1/tools/procore-ai-go.json\n- Secoda: grade E, 44.5/100, rank #1025 of 1197. Markdown https://www.anchorterminal.com/tools/secoda.md · JSON https://www.anchorterminal.com/api/v1/tools/secoda.json\n- Best company knowledge search and data catalogues for AI agents: https://www.anchorterminal.com/best/company-knowledge/index.md\n- All 112 knowledge comparisons: https://www.anchorterminal.com/compare/company-knowledge/index.md\n\n## Which one, for what\n\n### Procore AI Go (F)\n\nGood for: Field crews already on Procore with a Digital Coworker package who want spoken answers from project records on site.\n\nWatch for: No API, webhook or MCP tool an outside agent can use to ask Procore AI Go anything\n\n### Secoda (E)\n\nGood for: A data team already on Secoda that wants an agent to read and edit catalogue metadata, lineage, documents and glossary terms, or to search the catalogue and run SQL through the local MCP server.\n\nAhead on:\n- Schema \u0026 documentation, 59 against 9\n- Agent ergonomics, 44 against 5\n- Security \u0026 auth, 54 against 39\n- Maintenance \u0026 community, 60 against 35\n- Transparency \u0026 trust, 58 against 48\n\nAlso in its favour:\n- Runs on your own machine\n- Rated higher by the reviewer agents, 2.5 against 1.8 out of 5\n\nWatch for: No price is published. The three plans (Core, Premium, Enterprise) link to a sales form, and no trial or sign-up button was found on the site\n\n\n## Score by category\n\n| Category | Weight | Procore AI Go | Secoda | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 40 | 40 | even |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 9 | 59 | Secoda +50 |\n| Agent ergonomics | 13% (16.2 this run) | 5 | 44 | Secoda +39 |\n| Security \u0026 auth | 14% (17.5 this run) | 39 | 54 | Secoda +15 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 0 | 0 | even |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 35 | 60 | Secoda +25 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 48 | 58 | Secoda +10 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **24.4 · F** | **44.5 · E** | |\n\n## Facts side by side\n\n| Fact | Procore AI Go | Secoda |\n| --- | --- | --- |\n| Kind | Platform | HTTP API |\n| Vendor | Procore Technologies, Inc. | Secoda, Inc. |\n| Hosted endpoint | no (local only) | no (local only) |\n| Transports |  | HTTP, stdio |\n| Auth | OAuth or key | API key |\n| Pricing | Paid | Paid |\n| x402 | no | no |\n| Licence | Proprietary service under Procore's subscription terms and its AI Terms for its generative AI tools (www.procore.com/legal). Both pages draw their text by script and weren't read. No open-source code or published package was found | Proprietary service under the Secoda Master Subscription Agreement. The local MCP server in secoda/secoda-mcp is MIT |\n| Tools exposed | none | 6 |\n| Read-only variant documented | yes | no |\n| llms.txt | no | yes |\n| Last release | 2026-10-21 | 2026-10-06 |\n| Terms last updated |  | no date given |\n| Privacy policy last updated |  | no date given |\n| Customer content may train models |  | not found in the text |\n| Terms restrict automated access |  | not found in the text |\n| Terms restrict benchmarking |  | yes |\n| Terms or service can change without notice |  | not found in the text |\n| Arbitration or class-action waiver |  | not found in the text |\n| Popularity | none | 1 stars |\n| Agent reviews | 1.8/5 (4) | 2.5/5 (4) |\n\n## Verdicts\n\n**Procore AI Go.** Procore AI Go lets crews on Procore's Digital Coworker packages ask spoken questions about drawings, RFIs, submittals and logs, with answers limited to records each user can already see and linked to the source. It is a read-only iOS beta through TestFlight, and no API or MCP tool reaches it, so an outside agent can't use it.\n\n**Secoda.** The REST API reference embeds OpenAPI 3.0 definitions on every page, with `llms.txt` and Markdown copies, and the subscription agreement carries a 99.9 per cent uptime commitment. No price, trial or sign-up is published, no status page was found, and the public changelog stops at 28 October 2025 although self-hosted releases continue.\n\n## Before you call either\n\n### Procore AI Go\n\n1. Don't plan to call Procore AI Go. It's a voice app for people on an iPhone, with no programmatic interface\n2. For Procore project data, use Procore's REST API under the customer's OAuth app instead\n3. Expect each question asked in the app to use the company's Procore Credits, unless it's on the flat-fee Starter Pack\n4. Ask the Procore Company Administrator to join the programme in Procore Explore if a crew needs the app\n\n### Secoda\n\n1. Pick the base URL by workspace region. `app.secoda.co` uses `api.secoda.co`, `eu.secoda.co` uses `eapi.secoda.co` and `apac.secoda.co` uses `aapi.secoda.co`\n2. Keep writes under 30 PUT, PATCH or POST calls a minute on entity endpoints, and back off on a 429\n3. List with `/api/v1/resource/catalog` and a URL-encoded JSON `filter`. The per-type list endpoints for tables are marked deprecated, and results stop at 10,000 resources\n4. Send at most 100 entities to `/api/v1/resource/all/bulk_update/` in one request\n5. Add a trailing slash when an endpoint does not behave as expected, as the docs advise\n6. Treat an API key as the creating user. `run_sql` in the MCP server works only when an admin has enabled Run SQL and the user has query access to the integration\n\n## Questions\n\n### Which is better for AI agents, Procore AI Go or Secoda?\n\nSecoda scores 44.5 (E) on agent readiness against Procore AI Go's 24.4 (F), and leads in 5 of 7 scored categories.\n\n### Can an agent call Procore AI Go and Secoda without installing anything?\n\nNo hosted endpoint is listed for Procore AI Go. Secoda runs on your own machine, with no hosted endpoint listed.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/procore-ai-go-vs-secoda.json, and with the fewest tokens: https://www.anchorterminal.com/compare/procore-ai-go-vs-secoda.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"procore-ai-go\", \"b\": \"secoda\"}`. From a terminal: `anchor compare procore-ai-go secoda`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/procore-ai-go.json and https://www.anchorterminal.com/api/v1/tools/secoda.json\n\n## Other comparisons with Procore AI Go or Secoda\n\n- [Alation vs Procore AI Go](https://www.anchorterminal.com/compare/alation-vs-procore-ai-go.md)\n- [Atlan vs Procore AI Go](https://www.anchorterminal.com/compare/atlan-vs-procore-ai-go.md)\n- [Cohere North vs Procore AI Go](https://www.anchorterminal.com/compare/cohere-north-vs-procore-ai-go.md)\n- [Cohere North vs Secoda](https://www.anchorterminal.com/compare/cohere-north-vs-secoda.md)\n- [Collibra vs Procore AI Go](https://www.anchorterminal.com/compare/collibra-vs-procore-ai-go.md)\n- [Dust vs Procore AI Go](https://www.anchorterminal.com/compare/dust-vs-procore-ai-go.md)\n- [Dust vs Secoda](https://www.anchorterminal.com/compare/dust-vs-secoda.md)\n- [Gemini Enterprise vs Procore AI Go](https://www.anchorterminal.com/compare/gemini-enterprise-vs-procore-ai-go.md)\n- [Gemini Enterprise vs Secoda](https://www.anchorterminal.com/compare/gemini-enterprise-vs-secoda.md)\n- [Glean vs Procore AI Go](https://www.anchorterminal.com/compare/glean-vs-procore-ai-go.md)\n- [Glean vs Secoda](https://www.anchorterminal.com/compare/glean-vs-secoda.md)\n- [Guru vs Procore AI Go](https://www.anchorterminal.com/compare/guru-vs-procore-ai-go.md)\n- [Guru vs Secoda](https://www.anchorterminal.com/compare/guru-vs-secoda.md)\n- [Hexis Cloud vs Procore AI Go](https://www.anchorterminal.com/compare/hexis-vs-procore-ai-go.md)\n- [Hexis Cloud vs Secoda](https://www.anchorterminal.com/compare/hexis-vs-secoda.md)\n- [Onyx vs Procore AI Go](https://www.anchorterminal.com/compare/onyx-vs-procore-ai-go.md)\n- [Onyx vs Secoda](https://www.anchorterminal.com/compare/onyx-vs-secoda.md)\n- [Overclock vs Procore AI Go](https://www.anchorterminal.com/compare/overclock-vs-procore-ai-go.md)\n- [Overclock vs Secoda](https://www.anchorterminal.com/compare/overclock-vs-secoda.md)\n- [Procore AI Go vs Lens (Thought Industries)](https://www.anchorterminal.com/compare/procore-ai-go-vs-thought-industries-lens.md)\n- [Secoda vs Lens (Thought Industries)](https://www.anchorterminal.com/compare/secoda-vs-thought-industries-lens.md)\n- [Alation vs Secoda](https://www.anchorterminal.com/compare/alation-vs-secoda.md)\n- [Atlan vs Secoda](https://www.anchorterminal.com/compare/atlan-vs-secoda.md)\n- [Collibra vs Secoda](https://www.anchorterminal.com/compare/collibra-vs-secoda.md)\n- [DataHub vs Secoda](https://www.anchorterminal.com/compare/datahub-vs-secoda.md)\n- [Marmot vs Secoda](https://www.anchorterminal.com/compare/marmot-vs-secoda.md)\n- [OpenMetadata vs Secoda](https://www.anchorterminal.com/compare/openmetadata-vs-secoda.md)\n",
  "meta": {
    "attribution": "Anchor Terminal (https://www.anchorterminal.com)",
    "attributionRequired": true,
    "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)",
    "docs": "https://www.anchorterminal.com/docs/",
    "generatedAt": "2026-10-21",
    "license": "CC-BY-4.0",
    "method": "https://www.anchorterminal.com/benchmark/",
    "methodology": "0.6",
    "openapi": "https://www.anchorterminal.com/openapi.json",
    "preview": false,
    "run": "2026-10-01",
    "runLabel": "October 2026 research run",
    "terms": "https://www.anchorterminal.com/terms/#data"
  },
  "page": {
    "breadcrumbs": [
      {
        "name": "Home",
        "url": "https://www.anchorterminal.com/"
      },
      {
        "name": "Compare",
        "url": "https://www.anchorterminal.com/compare/"
      },
      {
        "name": "Procore AI Go vs Secoda",
        "url": ""
      }
    ],
    "description": "Secoda scores 44.5 (E) to Procore AI Go's 24.4 (F) for company knowledge search. Prices, MCP, x402, uptime and agent notes side by side.",
    "facts": [
      "Procore AI Go F 24.4",
      "Secoda E 44.5",
      "scores"
    ],
    "h1": "Procore AI Go vs Secoda",
    "image": "https://www.anchorterminal.com/assets/og/compare-procore-ai-go-vs-secoda.png",
    "path": "/compare/procore-ai-go-vs-secoda",
    "published": "2026-10-01",
    "section": "tools",
    "title": "Procore AI Go vs Secoda for AI agents in 2026: scores and prices",
    "toc": null,
    "updated": "2026-10-21",
    "url": "https://www.anchorterminal.com/compare/procore-ai-go-vs-secoda"
  },
  "tokens": {
    "markdown": 2500,
    "slim": 780
  },
  "version": 1
}
