Collibra vs Procore AI Go

Collibra

Each REST API has an OpenAPI 3.0 definition, the developer portal publishes llms.txt and Markdown pages, and every MCP tool carries read-only and destructive annotations. Access needs a sales contract, since no price, trial or self-serve sign-up is published, and no general API rate limit was found in the reviewed documentation.

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.

Collibra

1. Ask a Collibra administrator to register an OAuth application. Integration applications use client credentials, and MCP clients need a user application with a redirect URI
2. Reuse each access token for its 5 minutes. The token endpoint answers 429 once a client drains its pool of 100 tokens, refilled at 30 a minute
3. Page large reads with cursor= and sortField=ID. Cursor and offset parameters cannot be combined, and Search API limit plus offset cannot exceed 10,000
4. Keep Import API files to 10,000 assets or fewer and run at most 8 imports at once. Retry a job that fails on a concurrency error
5. Expect discover_data_assets and discover_business_glossary to consume Collibra Units and to need the dgc.ai-copilot permission. Use search_asset_keyword for free keyword search

Procore AI Go

1. Don't plan to call Procore AI Go. It's a voice app for people on an iPhone, with no programmatic interface
2. For Procore project data, use Procore's REST API under the customer's OAuth app instead
3. Expect each question asked in the app to use the company's Procore Credits, unless it's on the flat-fee Starter Pack
4. Ask the Procore Company Administrator to join the programme in Procore Explore if a crew needs the app