Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.

next
md 35 lines 1008 Bytes
Rendered Raw
1 # Python Provider Workflow
2
3 ## Create Or Locate A Provider
4
5 Run from `python/`:
6
7 ```bash
8 make create-provider name=<provider-name>
9 make create-provider name=<provider-name> agentic=true
10 ```
11
12 Provider packages live under `python/providers/`.
13
14 ## Implementation Rules
15
16 - Keep provider dependencies in provider package metadata unless shared tooling needs them.
17 - Preserve public import paths.
18 - Match framework-native conventions.
19 - Update docs/examples when public usage changes.
20 - Use `cross-sdk-parity` for providers with TypeScript counterparts.
21 - New providers or renamed provider packages usually need explicit entries in `python/noxfile.py`'s `type_inference` provider install list and checked-file list.
22
23 ## Verification
24
25 Run from `python/`:
26
27 ```bash
28 make chk
29 make tst
30 make type_inference
31 ```
32
33 For narrow iteration, use pytest markers or direct test paths that match the provider.
34
35 For release-facing package metadata, build first and then use `twine check dist/*` when distribution files are present.