trying to solve with capsolver standalone cloudflare even i inject the token it wont let me pass. even with fallback.
so i wanna learn about if it is possible to solve in every site?
but how can i do with same session with this user agent? because before this user agent i have my own user agent and im sending my creds with my spesific user agent but solver gives me another one and when i try to connect with that user agent wants me to solve again what am i doing wrong
Hi everyone! 👋
Are you looking for a professional website at an affordable price? You’re in the right place.
I’m an experienced web developer specializing in creating modern, fast, and fully responsive websites tailored to your needs.
I can help you build:
• Business Websites
• E-commerce Stores
• Portfolio Websites
• Blog Websites
• Landing Pages
• Fully Custom Websites
I also provide complete solutions including:
• WordPress development & customization
• Premium plugins at very low cost
• Fast, secure, and reliable web hosting
• Website redesign & speed optimization
You can also get CodeCanyon website scripts at very cheap rates, and I will fully set up, customize, and manage your complete website at a budget-friendly price.
My goal is to deliver high-quality work, clean design, and long-term support so you don’t have to worry about anything.
If you’re serious about building your website or want to discuss your idea, feel free to DM me anytime. Let’s turn your idea into reality!
You can get high-quality CodeCanyon website scripts from me at very affordable rates. I can also help you choose the right script according to your needs and assist with setup if required. Feel free to DM me for more details.
Hi, I’m a Japanese software engineer with 8 yrs experience building AI and web applications. I work with startup founders and product teams who need a strong technical partner to ship fast and build correctly from the start. My expertise lies in the development of web applications (dashboards/admin panels, e-commerce platforms, and social networks), API integrations (authentication systems and rest APIs), data pipelines (scraping, cleaning and storing data) and DevOps projects. These days, I've developed several AI products including Voice AI ( RVC, text->voice, voice assistant (bot), video translation app ), video/image generation tool, LLMs and trading bot etc (https://dev.aoi-webstudio.com). I'm just in the search of startups or developer teams to work with. Feel free to reach if you looking for engineering support or need reliable technical partner.
We are looking for a developer with strong experience in the eBay API, specifically the Payment Dispute API.
We currently have a Google Apps Script (GAS) + Google Sheets management system that tracks eBay case-open events.
The system is already mostly complete, and the existing codebase (largely AI-assisted) is successfully retrieving standard case/open data.
The remaining issue is retrieving Payment Dispute information correctly.
━━━━━━━━━━━━━━━
Current Situation
━━━━━━━━━━━━━━━
API in use:
* eBay Sell Fulfillment API (Payment Dispute sub-API)
Currently working:
* /payment_dispute_summary → works correctly (HTTP 200)
* /payment_dispute/{id} → works correctly with valid dispute IDs (HTTP 200)
Problem:
* /payment_dispute/search
→ returns HTTP 404 / 500 in production
→ endpoint exists in official eBay documentation, but does not function correctly in production
OAuth scopes:
* Required dispute-related scopes are already configured correctly
Data we want to retrieve:
* Dispute ID
* Order ID
* Buyer name
* Amount
* Reason
* Status
* Response deadline
* Open date
* Closed date
* Seller protection eligibility
Output destination:
* Append to the existing Google Sheets case-management sheet
━━━━━━━━━━━━━━━
Important
━━━━━━━━━━━━━━━
This is NOT a full rebuild project.
The existing system is already functioning, and we want to preserve the current structure as much as possible.
We are specifically looking for someone who can isolate and fix the Payment Dispute retrieval portion only.
Because eBay APIs can behave differently from the official documentation depending on environment, permissions, or production behavior, we strongly prefer developers with actual hands-on eBay API experience.
If you have any questions, feel free to contact us.
We look forward to hearing from you.
Ну такое, обычно под капотом сбор дотов или капча, там реально 100$ только если пахать 20 часов. Если хочешь норм залив, бери лучше прокси под задачу и делай с головой.
Ну да, за 300 баксов поклеить обои - это пока ты найдешь заказчика, уже три раза прокси сменишь. Лучше уж капчу решать или с прокси в фарме сидеть, там хоть стабильнее.
We are looking for an experienced AI/Backend Developer to build an internal AI knowledge platform integrating Local LLMs, Box, and multiple external AI services.
The goal is to provide 10–20 employees with a single internal interface where they can search and utilize company knowledge stored in Box, interact with local and external AI models, and generate answers and documents with clear source references.
Key requirements include:
- Local LLM deployment on Mac Studio (Ollama or similar)
- Box API integration and on-demand search across large-scale company data
- RAG, document retrieval, and reranking
- Integration with external AI APIs such as OpenAI/GPT, Gemini, Grok, etc.
- AI Router/Orchestrator for selecting or combining multiple models
- User authentication and permission-aware document access
- Conversation history, knowledge management, and audit logs
- API usage/cost tracking and security controls
- Backend/API architecture suitable for future expansion
We do not plan to download or embed the entire Box dataset. The preferred approach is to search Box on demand, retrieve only relevant documents, process/rerank them, and provide the necessary context to the selected LLM.
We would like to begin with a small PoC and expand to production after validating search accuracy, response quality, performance, security, and operating costs.
When applying, please briefly describe your experience with Local LLMs, RAG, Box or similar enterprise storage APIs, multi-LLM integration, and the technology stack you would recommend for this project.