u/Icy-Image3238

Hey y'all,

Context
I'm building an ai agent that needs read-only but long-lived access to user's Stripe, database, logs platforms. The specific type of the database or the log platform is not known in advance. I want the Agent to be able to determine & connect to any database / platform via a pre-determined connection methods - MCP, API token, etc.

After one-time connection / configuraion, agent then needs to be able to execute dispute management workflows some time in the future over the period of time the user is using the service. This means agent can wake up to do work 1 day, 7 days or even a month after initial configuration.

Problem

1. MCPs are great but tokens are short-lived -> I am building this on top of Cloudflare Agent SDK, which have great support for MCPs overall BUT the access tokens are short-lived. They expire much too soon. I do not want a workflow to fail because agent no longer has access to a resource.

What I am thinking [NEED FEEDBACK]

1. Either I have to implement a token refresh mechanism on my side that periodically refreshes MCP access tokens before they expire OR
2. Allow agents to connect to a resource via a long-lived token -> for example ask for a db connection string with read-only access when connecting to a db, instead of an MCP server OR
3. Ask users to provide a long-lived API token and then
   1. Agent uses this API token with MCPs -> but not all MCP servers support API tokens as auth method. Some / most use oauth these days OR
   2. Agent uses this API token to hit the service API endpoint

Is there anything I am missing? How are you guys solving for a long-lived agent access to a resource?

I've been looking into reimbursement tools (GETIDA, Refunzo, Jarvio etc) but from what I can tell they all focus on warehouse-side issues (lost inventory, damaged in FC, shipment discrepancies)

My bigger problem right now is buyer return fraud - people returning items for bullshit / invented reasons, items returned that aren't mine, "defective" claims on products I know are fine. I'm filing SAFE-T claims manually but it's taking hours every week and half get auto-denied on first try by Amazon.

Is anyone using a tool that specifically helps with the buyer fraud side? Something that flags suspicious returns, helps prepare SAFE-T claims, or tracks which ones need resubmitting?

Thx!

Hey, this year I've restarted selling on FBA after a long break (doing it since 2019). Chose a new niche, launched and been dealing with a wave of return fraud lately - classic switcheroos, items "returned" that aren't even our product, buyers using identical formatted messages to claim defects ("foul smell"), when I know for a fact this is not the case

I've been filing SAFE-T claims but my experience is mixed. Some get approved after 2-3 resubmissions, others get auto-denied and I gave up.

What's your experience? Do you manage to claw back these fraudelent refunds?

What actually made the difference when you submitted and got some money back? How many times did you have to resubmit before it went through? What evidence made the difference? (photos, weight discrepancy, tracking data?) In pct terms how much were you refunded?

What's your workflow / what do you do when you get a suspicious return? Do you inspect same-day, take photos, file immediately? Or do you batch them? Any tools or process that makes this less painful?

Trying to figure out if it's worth the time investment to systematically fight these or if the approval rate is just too low.

Super appreciate your replies and good luck to all of us!