digitalkin_proto
Python Generated gRPC client and server interfaces from Digitalkin's service APIs.
Installation
pip install digitalkin_proto
Overview
This package provides Python interfaces generated from Digitalkin's Protocol Buffer definitions, enabling seamless integration with Digitalkin services via gRPC.
Usage
Basic Import
import digitalkin_proto
from digitalkin_proto.agentic_mesh_protocol.module.v1 import module_pb2, module_service_pb2_grpc
Working with gRPC Services
Example for connecting to a gRPC service:
import grpc
from digitalkin_proto.agentic_mesh_protocol.module.v1 import module_service_pb2_grpc
from digitalkin_proto.agentic_mesh_protocol.module.v1 import module_pb2
# Create a gRPC channel and client stub
channel = grpc.insecure_channel('localhost:50051')
stub = module_service_pb2_grpc.ModuleServiceStub(channel)
# Create a request object
request = module_pb2.YourRequestType(
field1="value1",
field2="value2"
)
# Call the service
response = stub.YourServiceMethod(request)
print(response)
Development
Prerequisites
- Python 3.10+
- uv - Modern Python package management
- Task - Task runner
- rsync - For copying generated files
Note: buf and protoc are handled by the submodule via npx, no local installation needed
Setup Development Environment
# Clone the repository with submodules
git clone --recurse-submodules https://github.com/DigitalKin-ai/service-apis-py.git
cd service-apis-py
# Setup development environment
task setup
# Or use the quick dev setup command
task dev
Common Development Tasks
# Generate Python code from protobuf definitions
task gen
# Build the package
task build
# Run tests
task test
# Format code
task fmt
# Lint code
task lint
# Clean build artifacts
task clean
# Bump version
task bump-version -- patch
task bump-version -- minor
task bump-version -- major
Publishing Process
- Update code and commit changes
- Use the GitHub "Create Release" workflow to bump version (patch, minor, major)
- The workflow will automatically create a new release and publish to PyPI
License
This project is licensed under the terms specified in the LICENSE file.
3 maintainers
Metadata
3 maintainers
Release files for digitalkin-proto 0.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| digitalkin_proto-0.2.0.tar.gz | 132.2 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| digitalkin_proto-0.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 338.3 kB
Release files / digitalkin_proto-0.2.0.tar.gz
| Download URL | digitalkin_proto-0.2.0.tar.gz |
|---|---|
| Size | 132.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c2ed0d9ef10f5ee8d77689a072b11f7b46472da211eddafb5543ca5d18f3cbbd
|
|
BLAKE2b-256 checksum How to use checksums |
58df3a87e3c95ed5bb1beea6c599bd2bdc259bd5a7d8e6fb77a0bed66a2d2165
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Dec 8, 2025.
Transparency logRelease files / digitalkin_proto-0.2.0-py3-none-any.whl
| Download URL | digitalkin_proto-0.2.0-py3-none-any.whl |
|---|---|
| Size | 206.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
450aec3a70c46f3a48e537c322850eeba333762d809a1ddbc9ad853459a1e6fd
|
|
BLAKE2b-256 checksum How to use checksums |
bac33c2f68963932d7d897dc27f7a5794b5c881f0fdd68c454864781d909dd64
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Dec 8, 2025.
Transparency log
