Per-robot economic tracking for SME logistics deployments #16
FoundryNet
started this conversation in
Ideas
Replies: 3 comments
-
|
Hi, thanks for sharing this - it’s an interesting perspective and contribution. I’ll keep this discussion open for a while so others can take a look and share their thoughts, and then I’ll close the topic. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Agree, lets go :) |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Hey Artem,
Great to hear. The integration point for AMRs would likely be the task completion callback in your navigation or task execution pipeline. When the robot finishes a mission (delivery, inspection, pick cycle).
The relay API is in final testing this week for easier integration, but the raw python integration is live and operational if you'd like to check it out and work it that way.
You can find that here: https://github.com/FoundryNet/foundry_net_MINT/blob/main/FoundryNet%20API%20Client/foundry-client.py
Happy to walk through the architecture or share the relay API docs once they're live. What does your current task completion flow look like? Happy to collab on this if interested.
Cheers!
…On Sunday, March 22nd, 2026 at 10:23 AM, Artem ***@***.***> wrote:
Agree, lets go :)
—
Reply to this email directly, [view it on GitHub](#16?email_source=notifications&email_token=BW3EHPTFFMAR4ZSVCF55VBD4SAORDA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNRSGU4TOOBYUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVRTG633UMVZF6Y3MNFRWW#discussioncomment-16259788), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/BW3EHPVKUU6JEZRIDAWVV734SAORDAVCNFSM6AAAAACWTYB7ASVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTMMRVHE3TQOA).
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hey, great project. As SMEs deploy these AMRs for client logistics work, one challenge that scales quickly is proving to clients which robot completed which tasks and for how long. Built a ROS2 compatible settlement layer that generates verified timestamped records per completed job. Each robot builds a portable work history useful for service billing, utilization tracking, and equipment valuation. Lightweight integration, no modifications to your stack.
Core logic here:
https://github.com/FoundryNet/foundry_net_MINT/blob/main/FoundryNet%20API%20Client/foundry-client.py
Curious if per-robot economics is something your community is thinking about as these get deployed commercially.
Cheers!
Beta Was this translation helpful? Give feedback.
All reactions