Open source · Apache-2.0 · Runs in your own browser
An AI agent paid for real goods on Allegro. No human at checkout.
Open-source layer for the AI agent you already run. It reads your own notes first, picks the right item itself, puts it in the cart and pays on Allegro.pl in your logged-in Chrome — under a spending mandate you sign once. Cart approval: one word from you, or none at all if your mandate says so.
Updated 2026-09-05 · alpha v0.1.1 · 166 automated tests · 1 real payment
First autonomous payment
ALLEGRO.PL · 2026-09-05 Toggle anchors 15 × 3.10 Total 46.50 PLN Smart! delivery 0.00 PLN Saved card · no 3-D Secure No CAPTCHA · 0 human clicks PAID — "Zakup opłacony" Claude in Chrome, own profile
What keeps you in control
A spending cap you sign
Per item, per order, in total — checked before every pay click.
A kill switch that is a file
Create MANDATE_REVOKED and the next action is refused.
Your browser, your card
Selects a card already saved in your account. Never types card data.
Stops on any challenge
3-D Secure, CAPTCHA, re-login, a cart that differs from the plan.
Append-only audit log
Every action logged locally, redacted before it is written.
Receipts, not testimonials
What actually happened on 2026-09-05
The request: anchors for a TV on a drywall wall. On 2026-09-04 the agent read the owner's notes, researched Allegro and picked the offer. The owner approved with a single tap ("add to cart") and one condition: "pay without me, or the project has failed." On 2026-09-05 the agent — the Claude in Chrome extension inside his normal, logged-in Chrome profile — completed checkout and payment with no human input.
01 · read notes, pick the item
Project note "heavy load on drywall": engineering verdict = toggle anchors, 4 mounting points, double safety margin; plastic plugs rejected. The agent compared 53 offers on Allegro and picked a Smart! offer at the right price (2026-09-04).
02 · cart approved
The owner's whole involvement: one tap on "add to cart" for the agent-picked line. Three unrelated, unselected lines left untouched. With HUMAN_CONFIRM=0 in the mandate this step disappears.
03 · checkout
Delivery address and parcel locker pre-filled by the account. Default payment on the page was "Przelew" (bank redirect — unusable for an agent). The agent switched to "Karta płatnicza".
04 · select card
Saved-cards dialog. The agent selected a card already on file. No card number, no CVV typed — ever.
05 · pay
Clicked "Kupuję i płacę".
06 · confirm
"Zakup opłacony". Order present in "Moje zakupy". Delivery to a parcel locker, 0 PLN, next business Tuesday.
What did NOT happen
- — No 3-D Secure or bank SMS
- — No CAPTCHA, no bot wall
- — No new card, no BLIK code, no new fintech account
- — No prompt telling the model to "ignore its policy"
- — No refusal from the extension (the day-before assumption that it would refuse was wrong)
Honest caveats
- — The asa runtime CLI did not drive this purchase; the agent session drove the extension step by step. A CLI end-to-end live payment is the next milestone.
- — In this run the owner approved the cart with one tap; with HUMAN_CONFIRM=0 the mandate authorizes buying without that step, and the request is the last thing the user types.
- — One purchase, one account, one card: n = 1 on 3-D Secure frequency. The Allegro Pay rail is untested.
Why this and not another agent
Three things nobody else's shopping agent does
Sound familiar? You ask an assistant to buy something; it browses, compares — then hands you the cart. You buy the same adapter three times because no shop knows your drawer. You answer "which size?" for the tenth time although you wrote it down years ago. Manual shopping costs 20–40 clicks and your memory; vendor agents keep the mandate on their side, confirm every step, and mostly do not run in Poland. This project reads your notes before it reads the shop, pays with what you already have, and keeps the mandate with you.
It reads your knowledge store first.
Before touching a search box the agent opens your notes: what you own, sizes and standards you use, what you bought before and from whom, what you have too much of. The owner's vault shows the same tripod adapter bought three times and roughly a thousand surplus screws. The problem is not finding items — it is remembering.
context:brief → need: "M5 low nut DIN 439 A2" #3 2026-07 [profile] seller known, used 2× · category: fasteners #7 2026-08 [do-not-buy] countersunk screws — surplus ~1000 facts 2 · assumptions 1 · open questions 0
It uses your accounts, your prices, your loyalty.
Your logged-in Chrome, your saved card, your invoice settings, your Allegro Smart!. The planner groups lines per seller to cross your free-delivery threshold and fills the gap with something you already buy. The 2026-09-05 order shipped for 0 PLN instead of 10.95 PLN.
basket:plan → seller A · 3 lines · 52.40 PLN · Smart! ✓ · delivery 0.00 gap filled with a previously bought item per_item ✓ per_order ✓ max_items ✓ aggregate ✓
It actually pays — and you actually stay in charge.
Operator-style agents hard-wire "confirm before purchase". This one picks the item, fills the cart and pays autonomously within a mandate you signed — cart approval is one word, or nothing if the mandate says so — and stops on anything else: a bank challenge, a CAPTCHA or bot wall, a re-login, a cart that differs from the approved plan. The run stops and tells you in chat; on a bank 3-D Secure page the runtime waits up to 5 minutes for you, then stops with no retry. No server of ours, no telemetry: your notes and page content go only to the LLM provider you already use.
MANDATE_REVOKED present → STOP (exit 2)
{"event":"mandate_checked","ok":true,"amount_pln":46.5,"remaining_pln":"[REDACTED]"}Context-first, in practice
"Buy X" — and it never asks what size
One rule in every example: the request is one sentence; every attribute comes from your notes; if a critical attribute is missing, the item is skipped with a one-line note instead of a question. Only the anchors have actually been paid for.
“Order a spare set of bed sheets.”
Looked up: bed 180×200 with lift-up storage, pocket-spring mattress ~22–25 cm, second bed 90×200, default colour on record
Would buy: fitted sheet 180×200 with ≥25 cm depth, matching duvet and pillow set, one Smart! seller over the free-delivery threshold
Did not ask: "What size is your bed? How thick is the mattress? Which colour?"
Status: vault-grounded, planner-tested, not bought
“Get the anchors for the TV wall.”
Looked up: note "heavy load on drywall": toggle anchors, 4 points, double safety margin, plastic plugs rejected
Would buy: 15 toggle anchors, 46.50 PLN, delivery 0 PLN — the real run: the agent picked the offer from the notes and Allegro, the owner approved the cart with one tap, the agent chose delivery and payment and paid
Did not ask: "Drywall or concrete? Which diameter? How many?"
Status: bought 2026-09-05
“Buy the dried fruit.”
Looked up: cherries, pitted prunes, black currants, raisins; assumptions written down: ~500 g packs, sultanas, dried not freeze-dried
Would buy: plan: one Smart! order at the seller that has three of four; currants separately; upgrading cherries 250 g → 500 g beat paying for delivery
Did not ask: "Which brand? Pack size? Pitted or not?"
Status: planned — real search log 2026-09-04, not bought
“Reorder filament.”
Looked up: two printers (X1C with AMS, H2C dual-nozzle), Ø1.75 mm, "almost always black", norms per material, previous seller, do-not-buy line: ~12 kg PET-G surplus
Would buy: 2 × PA12 black 1 kg from the previous seller; PET-G refused
Did not ask: "Diameter? Colour? Brand? Do you still have PET-G?"
Status: vault-grounded, planner-tested, not bought
“Top up the workshop consumables.”
Looked up: norms table: PVP glue stick 40–43 g ×2, indicator silica gel 200 g, IPA 99.9 % 500 ml, black 3:1 glue-lined heat-shrink
Would buy: all four at one Smart! seller, gap-filled with an item bought before
Did not ask: "Which glue? What purity? Which colour?"
Status: vault-grounded, planner-tested, not bought
“Spare props and connectors for the drone.”
Looked up: FPV build list: 9×5×3 tri-blade props, 6S packs, "XT60 only genuine AMASS"
Would buy: 2 prop sets in the recorded size + one pair of genuine XT60
Did not ask: "Which prop size? Genuine or clone?"
Status: vault-grounded, planner-tested, not bought
“Order the O-rings for the enclosure.”
Looked up: bill of materials of a weather-proof camera case: Ø62 O-rings in three sections and materials, silicone cord by the metre, M20×1.5 IP68 glands ×10, previous sellers
Would buy: exact sections and pack sizes at the sellers on record
Did not ask: "Inner diameter? Cross-section? Material?"
Status: vault-grounded, planner-tested, not bought
“Dowels for the tool wall.”
Looked up: wall type — not in the notes
Would buy: nothing. Reply: "didn't take: dowels — need wall type (drywall / brick / concrete)"
Did not ask: That is the whole failure mode: a skipped line, not a guess and not a questionnaire.
Status: the refusal path
Clothes and shoes are never offered — sizes are not in the store yet. Nothing here is a marketing invention: examples 1 and 4–7 come from the owner's real notes; the dried fruit was planned; the anchors were bought; the dowels show the refusal path.
Mechanism
How it works, in seven steps
The deterministic parts — mandate hash, context gate, allowlists, checkout steps, pay click, audit log — live in a small runtime. Your agent decides only at branch points.
01
You sign a mandate once
PURCHASE_MANDATE.md: limits, categories, marketplaces, validity, one-time ceiling. Hash-verified before every payment.
02
The agent reads your context
asa context:brief searches your notes for the need and records facts, assumptions and open questions. No brief, no search.
03
It searches in your browser
Results filtered by the mandate, ranked with your history and your do-not-buy list.
04
It plans the basket and fills the cart
One seller over the free-delivery threshold, at most a few complements you have bought before. Either one proposal message you approve with one word — or no question at all, if your mandate says so.
05
It checks the cart
Seller, price, quantity, condition, delivery cost against the approved plan. Any deviation is a stop.
06
It pays with your saved card
Bank 3-D Secure is handed to you and the runtime waits up to 5 minutes. CAPTCHA or block page: stop.
07
It logs and reports
Append-only, redacted JSONL; the purchase is added to your history so the next brief already knows.
Human only on: a bank challenge, a CAPTCHA or block page, a deviation from the mandate — and on cart approval if you keep HUMAN_CONFIRM=1. With HUMAN_CONFIRM=0 the request is the last thing you type.
You stay in control
Autonomy ends exactly where your mandate ends
Most people would not let an agent pay on its own — and without limits they are right. Every safeguard below is on by default; none can be switched off by the model, only by you editing a file.
One signed file.
PURCHASE_MANDATE.md lives outside the repo: per-item, per-order and aggregate limits, validity, categories, marketplaces, forbidden actions, a one-off approval ceiling. The SHA-256 of sections 1–6 is verified before every payment; change one byte and the runtime refuses to pay until you re-sign.
asa mandate:check --amount 46.50 --category hardware --domain allegro.pl → OK · remaining [REDACTED]
Limits that hold even when you say "just this once".
A one-off approval is capped by a ceiling you signed and raises the item and order limits for that run only — never the aggregate. A security review found exactly that bypass before any money moved; it was fixed and is covered by tests.
asa override --amount 120 --by "you (chat)" → item and order limits only; the aggregate limit still applies
Kill switch that is a file.
Create MANDATE_REVOKED next to the mandate; the next action is refused. Delete it to resume. No dashboard, no account.
touch MANDATE_REVOKED # revoked; delete the file to resume
Hard stops, not judgement calls.
Bot-protection or CAPTCHA page, logged-out state, a selector the runtime cannot resolve, any host outside the allowlist during payment, a declined payment or timeout → STOP. Planned, not yet in code: prompt-injection detector, new-device and auto-added-service detection.
Your card never enters the model.
The agent selects a card already saved in your account. Entering card data, CVV or one-time BLIK codes is forbidden by the mandate and not implemented in the code. A bank-transfer redirect is refused as a rail, not attempted.
Append-only, redacted audit log.
Every action is written locally as JSONL; every line passes a redaction filter before it is written, and a separate redacted monthly export is what you share. Address-like fields stay out of the log; stored page snapshots exclude payment forms.
asa audit:redact --month 2026-09 → measurements/audit-2026-09.redacted.jsonl
Your browser, your accounts — nothing anti-bot.
It runs in your own logged-in Chrome. No headless browser against a marketplace, no proxies, no anti-detect, no fingerprint spoofing, no CAPTCHA solving — permanently out of scope. If the site says stop, the agent stops.
Template with example values (not the owner's signed file)
Single-item limit: ≤ 60 PLN
Single-purchase limit: ≤ 100 PLN
Aggregate mandate limit: ≤ <M> PLN
Validity: <from> – <to>
Marketplaces: allegro.pl
Payment instrument: saved card only
Prohibited: subscriptions, digital goods, age-restricted,
new card data, one-time BLIK codes,
external payment links, order splitting
One-time approvals: ≤ <N> PLN, in chat, per run
SHA-256 (sections 1–6): verified before every paymentThe whole approval UI is one reply
ok = approve · ok B = take option B · ok without 3 = drop line 3 · ok 84,90 = approve with a one-off ceiling · no = cancel · item limit 120 = amend, re-hash, re-sign
Run it yourself
For humans, and for your AI agent
You need Chrome with the Claude in Chrome extension, Node 20, and an Allegro account with a card already saved. Two paths exist: the extension-driven flow (the one that has paid) and the asa runtime (tested offline, no live CLI payment yet). The agent-readable version is one prompt you paste.
For humans
Verified on Windows 10; macOS and Linux untested for the checkout channel. Start with a category you can afford to get wrong and 20 minutes.
git clone https://github.com/AndriiShramko/agentic-shopping-autopilot cd agentic-shopping-autopilot/runtime npm install && npm test && npm run build
- Clone and prove the build: npm install && npm test in runtime/ — no marketplace traffic. If it is not green, stop and open an issue.
- Install the skill: copy skills/allegro.pl/ into ~/.claude/skills/ (Claude Code) or your agent's skills folder.
- Create a private folder outside the repo (default ~/.asa/private or ASA_PRIVATE_DIR). Copy examples/PURCHASE_MANDATE.template.md there and fill in limits you would not mind losing — start at 20 PLN per item, 40 PLN aggregate, one category, allegro.pl, 7 days.
- Point the agent at your notes: CONTEXT_STORES=obsidian:<path to your vault> in config.env (never commit it). Run asa profile:check and asa context:brief --need "test" — the context gate is now live.
- Sign: the agent shows you the mandate text and its SHA-256; confirm the hash in chat; asa mandate:sign. Keep the file unchanged afterwards.
- Dry run: ask for a search-only task ("find a Smart! offer for a PVP glue stick 40 g, do not buy"). Read the proposal and the audit line.
- First live run with HUMAN_CONFIRM=1: everything up to the pay button, then it waits for you. A bank page, CAPTCHA or re-login prompt is your job — the agent says so and waits.
- Afterwards: confirm the order in "Moje zakupy", read the audit JSONL, and — if you can — share a redacted receipt in an issue.
For your AI agent
Paste this into Claude Code (verified) — Codex, Cursor and Gemini CLI read the same files and should work (untested for purchases). The prompt never asks the agent to pay: you sign, and you run the first live purchase.
Install Agentic Shopping Autopilot for me. Read https://raw.githubusercontent.com/AndriiShramko/agentic-shopping-autopilot/main/AGENT_SETUP.md and follow it step by step. Ask me only at the decision points it lists (limits, categories, marketplaces, validity, the path to my notes). Never type card numbers, passwords or one-time codes. Never bypass a CAPTCHA, a bot page or 3-D Secure. Do not run asa mandate:sign until I write "ok <hash>" in this chat, and do not buy anything in this session. Report "installed" only when asa mandate:check and asa browser:check are green. Machine-readable docs: https://agentic-shopping.flyreelstudio.eu/llms.txt
To stop at any time: create MANDATE_REVOKED in the private folder. To uninstall: delete the private folder and the skill folder. Nothing else was installed.
Updates: git pull --rebase, then npm install && npm test, then read CHANGELOG.md. Re-sign the mandate only if the changelog says its format changed. Share fixes back through CONTRIBUTING.md.
Read this before you run it
Twelve things that can go wrong
Alpha software with one real purchase behind it. Every transaction under your mandate is your transaction. The author accepted these risks for his own account; nobody can accept them for yours. This page is not legal advice.
- 01Marketplace terms. Allegro's regulation (effective 2026-09-01) says automated tools are used at your own risk (art. 2.8), bans data extraction (art. 10.10) and bots or software tools used in connection with Allegro (art. 10.11); Allegro may block such tools (art. 8) and suspend accounts. Possible outcome: temporary or permanent loss of the account, Smart!, ratings and history.
- 02Wrong item, quantity or variant — inside your limits, it is yours. Grouped product pages, variant pickers and quantity fields are only partly automated. The agent re-checks seller, price, condition and lines before paying; mistakes remain possible. Your mandate limits are your real protection.
- 03Responsibility stays with you. A terms breach is your contract with the marketplace; a payment under your mandate is your payment. No Polish or EU case law on agent purchases exists yet.
- 04Allegro Pay and fraud scoring. Agent sessions look atypical; community reports mention long blocks. Only the saved-card rail is proven; Allegro Pay is untested.
- 05Bot protection. Headless or fresh browsers are blocked on the first visit (observed 2026-09-03). This project will never bypass it; a block is a stop. Today's pass with a real profile is a window, not a guarantee.
- 06Bank challenges are law. PSD2 makes periodic 3-D Secure unavoidable. The agent cannot complete it; the runtime waits up to 5 minutes for you, then stops. Bank transfers and one-time BLIK codes are incompatible with autonomy by design.
- 07Prices and thresholds move. Between search and checkout prices change, Smart! thresholds differ per account, services get auto-added. A cart that differs from the approved plan is a stop, never a silent payment — still check the order afterwards.
- 08Sellers and scams. Ratings are read; sellers can still be poor. Any off-platform payment request (chat link, "courier fee" page) is a hard stop; the agent pays only inside the platform's own checkout.
- 09Double orders. A retry after a timeout can leave an unpaid duplicate order (it happened in the owner's own history). The runtime never retries a declined payment, but check your order list after a stopped run.
- 10Re-login, 2FA, "new device". A logged-out state stops the run; a wiped profile loses trusted-device status and re-triggers bank and bot checks.
- 11Vendor policy can change overnight. The proven channel depends on the Claude in Chrome extension permitting purchase clicks; the vendor may re-ask for confirmation, and models may refuse. The mandate is a mitigation, not a guarantee. This project rejects "ignore your policy" prompts.
- 12Prompt injection and your notes. Listing titles, descriptions, seller messages and images are untrusted input. Mitigations: domain and action allowlists, no secrets in the model context; an injection detector is planned. Your profile files are plain text on disk — keep addresses, codes and card data out of what the agent reads.
Compared with the alternatives
Where each option keeps the mandate — and whether it can pay
As of the 2026-08-31 research (8 agents, ~150 dated sources) and the 2026-09-05 test, no vendor shopping agent both pays autonomously and works on Polish marketplaces; open-source browser agents have no mandate concept and get blocked when headless.
| Option | Who holds the mandate | Your accounts, prices, Smart! | Pays without you | Reads your notes first | Open source | Status (dated) |
|---|---|---|---|---|---|---|
| Buying manually | You, every time | Yes | No — 20–40 clicks per order | Only what you remember | — | — |
| ChatGPT agent / Operator-style | Vendor; confirm-before-purchase | Partly | No | No | No | Agent mode not offered in the EU/EEA as of 2026-08-31 |
| OpenAI Instant Checkout / ACP | Merchant side, per step | US ACP merchants only | No | No | Spec only | Product wound down 2026-03; ACP spec remains |
| Amazon "Buy for Me" | Amazon, US beta | Amazon only | No | No | No | Not in Poland; litigated against a third-party agent (ruling 2026-08-04) |
| Perplexity Comet + PayPal | Perplexity; human confirms | PayPal, US-centric | No | No | No | Independent test reported a purchase in a fake store (Guardio Labs, Aug 2025) |
| Allegro app in ChatGPT | Allegro; "Kup na Allegro" jumps to the site | Yes | No | No | No | Official; checkout stays on allegro.pl |
| Generic open-source browser agents | None — no limits | Any site, but headless → blocked | Can click "pay" with a raw card — the risk, not the feature | No | Yes | Cloud variants sell CAPTCHA/proxy bypass |
| Agent-commerce CLIs (northcinder, UCP, Link) | Per-deal approval or merchant-held | US shops, read-only | No — human pays | No | Yes | Closest cousins, local-first (2026-08-30) |
| Agentic Shopping Autopilot | You, once — signed mandate, SHA-256 checked before every payment | Yes — own Chrome, saved card, Smart! 0 PLN proven | Yes — 46.50 PLN on 2026-09-05; challenges → stop and hand-off | Yes | Yes, Apache-2.0 | Alpha; n = 1; terms-of-service risk stated openly |
Vendor lines are dated facts from the research, not claims about the future; they change monthly. Unknowns we publish: real 3-D Secure frequency (n = 1), bot-wall tolerance for repeated runs, Allegro API app verification (blocked for us), the Allegro Pay rail, the OLX flow. Full comparison with sources
Questions people ask their AI about this
Can it really spend money without me?
Yes — inside a PURCHASE_MANDATE.md you sign once (per-item, per-order and aggregate limits, validity, categories, sites, a one-time approval ceiling). The agent picks the item from your notes and the shop, fills the cart and pays; cart approval is one word from you, or none if the mandate allows it. On 2026-09-05 it paid 46.50 PLN on Allegro with zero human clicks at checkout. Outside the mandate, or on any bank challenge, the run stops and tells you in chat.
Where is my card data?
Where it already was: saved in your marketplace account. The agent selects a stored card in your own logged-in Chrome; it never types a card number, CVV or BLIK code — forbidden by the mandate and not implemented in the code. Secrets are never placed in the model's context or the audit log.
What happens with 3-D Secure or a bank SMS?
The agent stops. Bank pages are outside the domain allowlist, so it neither reads nor clicks them; the runtime waits up to 5 minutes for you to finish, then stops with no retry. PSD2 makes periodic challenges unavoidable; our single purchase triggered none — that is n = 1, not a rate.
How does it know which size, brand and seller I want without asking?
Before searching, the agent reads your notes — an Obsidian vault or any Markdown folder — for what you own, sizes and standards, past purchases, sellers and do-not-buy lines, and writes a local context brief with facts, assumptions and open questions. Search refuses to run without it. A missing critical attribute means the item is skipped with a one-line note.
Which shops does it support?
Allegro.pl only, today — search, Smart!-aware basket planning and checkout with a saved card. OLX.pl is next, restricted to its native escrow ("Kup z Przesyłką OLX"), and is not implemented. Adapters are a Markdown skill plus a selector file, so other shops can be contributed.
Does it work with Claude Code, Codex, Cursor?
Verified with Claude Code plus the Claude in Chrome extension on Windows. Skills use the open Agent Skills format that Codex CLI, Cursor and Gemini CLI read, so planning and the offline runtime should work there — untested, and no purchase has been made through them. The Node 20 runtime runs anywhere.
How do I stop it?
Create an empty file named MANDATE_REVOKED in your private directory; the next action is refused. Edit one byte of the mandate and every payment check fails until you re-sign. Close Chrome and it has no hands. Uninstall is deleting two folders — no service, no account, no server.
Is this allowed by Allegro's terms?
Uncertain, and the risk is yours. The regulation effective 2026-09-01 puts automated tools at the user's risk (art. 2.8), bans scraping (10.10) and bots or software tools used in connection with Allegro (10.11), and lets Allegro block tools (art. 8) and suspend accounts. The often-quoted "no orders without a human" sentence does not exist there. Not legal advice.
Is it really open source? Which license?
Yes. Code is Apache-2.0, documentation CC BY 4.0, repository AndriiShramko/agentic-shopping-autopilot. Your mandate, buyer profile and audit logs live in a separate private directory that is never committed. No hosted service, no account, no telemetry; your notes reach only the LLM provider you already use.
Why trust a project with one real purchase?
Don't trust — verify. The receipt, the flow and every caveat are published; the runtime has an offline test suite; a security review caught an aggregate-limit bypass before any money moved; the risk box lists twelve known problems before you ask. Run it in dry-run mode with a 20 PLN cap and read the audit log yourself.
Author
Built by a buyer, not a demo — and open to interesting acquaintances
I'm Andrii Shramko, a Poland-based maker-founder. I build products end-to-end with AI agents: this project; the SpatialCart Protocol (phone room scan → measurable spatial database → fit-verified multi-store order — this agent is its execution leg); a crowd light-show platform; a 3D-Gaussian-splat browser game of my own city; an industrial vision safety-patrol product — all under flyreelstudio.eu with the same method used here.
- The knowledge store this agent reads is my real workshop memory: two Bambu Lab printers, FPV builds, a 20-camera GoPro rig, weather-proof camera enclosures with full bills of materials.
- Research first: 8 agents and ~150 dated sources before a line of code; primary sources over press.
- A rule of never reporting anything I haven't verified — which is why the receipt above comes with its caveats.
I'm always open to interesting acquaintances and ready to help teams build incredible projects — as a partner, a builder, or the person who assembles and leads the team: agentic commerce, site-skill registries, spatial commerce. Marketplaces, payments teams, researchers, founders who want an agent that actually finishes the purchase: write to me.
- Author
- Andrii Shramko
- linkedin.com/in/andrii-shramko
- Book a call
- calendar.app.google/Ff729HqGk4RpzPNDA
- zmei116@gmail.com
- GitHub
- github.com/AndriiShramko
Get in touch
Tell me what you want to do with it
One message, a few taps. You get a personal reply and, if you want it, the next receipt or early access to the OLX adapter. I read every submission myself — usually within two working days.