Skip to main content

gatecore-crewai

gatecore-crewai provides three CrewAI tools for GateCore marketplace discovery and procurement, plus helpers that execute a procured capability through GateCore's signed gateway. The adapter contains transport and configuration only; GateCore services enforce identity, policy, trust, pricing, funding, delegation, and settlement.

The MCP tools support public full-mode GateCore endpoints only. read mode passes the server's fail-closed procurement error through unchanged. off mode is unsupported because it does not replace the adapter's legacy placeholder identity with the MCP credential identity.

This package intentionally duplicates the small adapter configuration, execution, and transport modules. A shared adapter-core package is a future decision that waits until a third framework adapter establishes the common surface.

Install from the GateCore monorepo

python -m pip install -e ./libs/sdk -e ./libs/adapters/gatecore-crewai

Install from PyPI (effective on publish)

Effective once gatecore-sdk and this package have a real PyPI release — see .github/workflows/publish-pypi.yml. Until then, use the monorepo install above.

python -m pip install gatecore-crewai

Configuration

Discovery and procurement require:

GATECORE_MCP_URL=https://mcp.example.com/mcp
GATECORE_MCP_KEY=gcmk_...

execute_procured and aexecute_procured validate these variables lazily on first use:

GATECORE_GATEWAY_URL=https://api.example.com
GATECORE_BEARER_TOKEN=...
GATECORE_AGENT_ID=agent:example
GATECORE_ACCESS_GRANT_ID=grant:example
GATECORE_KEY_ID=key:example
GATECORE_PRIVATE_KEY_PATH=/secure/path/agent-key.pem

Set exactly one of GATECORE_PRIVATE_KEY_PATH or GATECORE_PRIVATE_KEY_PEM.

Usage

from gatecore_crewai import GateCoreToolkit, execute_procured

tools = GateCoreToolkit().get_tools()
procure_result = tools[2].run(listing_id="listing:example")
decision = execute_procured(procure_result, {"query": "example"})

CrewAI tools are sync-native. Their synchronous implementation uses asyncio.run() for the MCP transport and therefore must not be called from a thread that already owns a running event loop; use arun() in async applications.

Release files for gatecore-crewai 0.1.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for gatecore-crewai 0.1.1
File Size Uploaded
gatecore_crewai-0.1.1.tar.gz 11.3 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for gatecore-crewai 0.1.1
File Interpreter ABI Platform
gatecore_crewai-0.1.1-py3-none-any.whl Python 3 none any Details

Total release size: 20.1 kB

Release files / gatecore_crewai-0.1.1.tar.gz

Download URL gatecore_crewai-0.1.1.tar.gz
Size 11.3 kB
Tags Source
SHA-256 checksum
How to use checksums
8816a52ea17d4019ec859bd1828577293cafd0da237a092ef82024772aa44f77
BLAKE2b-256 checksum
How to use checksums
13c17604574046b9c60e274235e440e84ddbb260a76102bfa3abcb7b585c1293
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Aug 20, 2026.

Transparency log

Release files / gatecore_crewai-0.1.1-py3-none-any.whl

Download URL gatecore_crewai-0.1.1-py3-none-any.whl
Size 8.7 kB
Tags Python 3
SHA-256 checksum
How to use checksums
8872397e3af83b880536b508721aaaa2f4f59152f9d6f648814cde42c83c1f2d
BLAKE2b-256 checksum
How to use checksums
05b52cf73059cae26d069b2678ae54da083edd4f2f935d5fcf5104b80c959e50
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Aug 20, 2026.

Transparency log

Release history Release notifications | RSS feed

0.1.3

2 release files

0.1.2

2 release files

This release

0.1.1 This release

2 release files

0.1.0

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page